|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1948 | minor | always | 08-16-07 09:47 | 08-21-07 11:12 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.2 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.3 | ||
|
|
|||||
| Summary: | 0001948: Hessian final arg can be InputStream | ||||
| Description: |
(rep by Compl Yue Still) Hi, another idea regarding Hessian. I'd think it's feasible to implement the client interface of hessian that when the service method takes its last argument as InputStream or Reader, or return InputStream or Reader, the binary or character streams are automatically wrapped. I don't know if this feature is already implemented by 2.0 or 1.02, seems it is not by 1.01 coz the "Hessian with large binary data" section is still in the user guide (http://www.caucho.com/resin-3.0/protocols/hessian.xtp). [^] I don't think this hack is needed if InputStream and Reader are properly wrapped. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | hessian/348{2,3} | ||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |