Paul, Right now I can live without streams because its easy enough to create a method like byte[] read() that you can call multiple times. This is what we have been doing with EJB for awhile.
I don't use callbacks in any of my current projects, but that may be because most envrionments dont support it. I bet there are other people who could really use that. One thing that will need to be fixed is that in java 1.4 exceptions now can wrap another exception to get a it's stack trace. The problem comes up when an exception that a remote method can throw wraps an exception that the client dosent have. Example: server side code throws a SybaseSQLException, which the server wraps into some ServerException. When the client gets the exception it creates the ServerException no problem, but gets a NoClassDefFound when it tries to create the wrapped SybaseSQLException. The fix would be to override the serialization of exceptions to just include the text of the wrapped exceptions. -mike > Mike, > > Applied thanks. Though the file you supplied was on an older > version of > the the tranport package. > > In use what most annoys you about 'transport' and AltRMI ? > > * lack of callbacks > * lack of support for streams (as parameters or return types) > * something else? > > - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
