Yeah! that could go much further than just "constants", anything that might be used more times without varying.. After this post, I'm figuring out that I can put resolved Class and Method objects in the "constant" pool instead of just type and method names, so the resolution could also be accerlerated here.
In fact I'm prototyping a new framework that somewhat different than conventional approaches, and for some reasons hessian can''t be just used underneath as a whole without change, so I'm actually deriving my wire protocol from hessian.. Maybe some off topic, the idea I'm prototyping is called "Hosting Based Interfacing" by far, that to enable inter-operations between distributed software components in ways other than "Invocation Based Interfacing", the benefits would be (overall) simplified development and performance boost. Why and how is some long to explain, but the basic idea is to let each component provide its local domain environment for hosting of "Task Agent" objects (which just carry exectuable logics for specific tasks) originated from other components' domains, the hosted task agent objects are originated from a component domain and executed locally at their target domains (some akin to stored procedures, but here each component can act as the SQL server), they produce new agent objects to send back instead of just return a result. This should ideally reduce round trips of communication and allow business logics (beared by local domains and task agents) to grow without burden from static contracts as "invocation interfaces", and its asynchronous nature should match well with RIAs where synchronized, distributed transactions are less required. Cheers, Compl On 8/11/07, Emil Ong <[EMAIL PROTECTED]> wrote: > Hi Compl, > > This is a pretty interesting idea. I would rephrase it as adding > instance references rather than constants. Scott, what do you think? > > There are a couple of possibilities in the meantime. Basically the > compression you're suggesting is like an explicit form of gzip (sort > of), so you could just use gzip for your application now. The other > thing we've got going is a Hessian/REST implementation that features > caching for HTTP GETs. That would reduce processing time in certain > applications. > > Thanks for the suggestion! > > Emil > > ============================================================ > > Emil Ong > Software Engineer > 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
