[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.6

Handling Chunked Response in Web Service Client

Asked by ToddBPeterson in HTTP, Web Services and WCF, SOAP

Tags: Web Service Java .Net BEA SOAP HTTP XML

Our company has been developing and consuming web services, "internally", for a couple of years now.  We've recently run into an issue where the XML response, consisting of a base64encoded PDF document, is being chunked by the server.  Inspection of the HTTP headers indicates "Transfer-Encoding=chunked".

Our web service clients are based on the BEA ClientGen task, which doesn't seem to support chunked responses well, vs. something like Axis2.  The problem with Axis is that it is open source, which is difficult to get approval for, in our organization.

Options that have been considered are:
1. Turn off chunking on the server side - This seems more like a knee-jerk response, with potential performance implications, to support one client
2. Take on the red-tape challenge and see if we can get approval for Axis, for this client
3. De-chunk the data in code, after receiving the response

How are other folks (web service clients) deailing with chunked responses?  Are there tricks in the client generation that make the chunk handling/marshaling transparent?  How about de-chunking the data in code?  Does anyone have any examples of code to de-chunk the response data?

Any information or suggestions regarding best practices or solutions are greatly appreciated!

Best Regards,
Todd
[+][-]08/10/09 03:30 AM, ID: 25058542Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: HTTP, Web Services and WCF, SOAP
Tags: Web Service Java .Net BEA SOAP HTTP XML
Sign Up Now!
Solution Provided By: BigRat
Participating Experts: 1
Solution Grade: B
 
 
Loading Advertisement...
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625