On Tue, Dec 04, 2007 at 10:36:29PM +0000, Ben Hood wrote: > > What I am trying to say is that the processing side of the application > needs to be architected around a streaming principle to benefit from > any streaming ability in the protocol.
That's exactly right. One of the motivations that I didn't really go into is also that this change makes it much easier to write a streaming reader when dealing with non-blocking I/O. That is to say, it makes reading much easier for Flash ;-). Flash is completely non-blocking and if we didn't know where object boundaries were, we would have to restart parsing objects every time we received data. Putting things in packets basically gives the encoded length of the object, which means we don't need a stateful parser. We can just buffer until the whole object is there, then use the existing parser on that buffer. As far as simplicity, I think given the goal of giving the encoded object length, this approach is about as bare-bones as you can get. Thanks for the comments! Emil ============================================================ Emil Ong Chief Evangelist Caucho Technology, Inc. Tel. (858) 456-0300 mailto:[EMAIL PROTECTED] Caucho: Reliable Open Source --> Resin: application server --> Quercus: PHP in Java --> Hessian Web Services _______________________________________________ hessian-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/hessian-interest
