Vinay, > <snip> > >> Right now CallbackEnabled client stream treats > >> ALL of > >> its arguments , which are interfaces , as > >> pass by reference > > This is only for the callback object on the > > CallbackEnabled stream, correct? > > Yes. > Other streams treats every argument as > pass-by-value and serializes it across.
Not true. If a parameter going back to the server from a client originated from the client in that AND it was a pass-by-reference boundary, then it is not serialized (or transported as is). Instead it is swapped for a it's original refernece. Swapped in that there is an array of the args going back to the server for each method call. > I shall look into the other improvements I talked off > as soon as I am done with writing stub-generators > using BCEL. Excelent work dude. I did not think it was possible. I am not worthy etc... -ph __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
