|
Mantis - Hessian
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3579 | major | always | 06-25-09 19:43 | 08-28-09 08:51 | |
|
|
|||||
| Reporter: | rmann | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.0 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.1 | ||
|
|
|||||
| Summary: | 0003579: v1.0 requests seem to result in transfer-coding chunk size of 1 byte, dramatically increasing payload size | ||||
| Description: |
I'm experiencing a situation where making a v1.0 request against my Hessian service results in half of the response being sent in single-byte chunks. This at least doubles that portion of the payload, since HTTP requires a chunk length byte for every chunk. Test code that fetches using the 3.2.1 hessian Java library, and presumably uses 2.0, behaves much better in this regard. The 1.0 client code is HessianKit (Objective C), used on the iPhone. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |