Wednesday, January 10, 2001, 2:24:50 PM, you wrote:
> To be picky, RMI cannot be slow, since it's only an interface
> specification. An RMI implementation can be slow, but that's another
> thing completely.
precise definition :) that's what I've meant
> This is precisely what the JBoss+EmbeddedTomcat integration provides. To
> be precise, the integration allows two things:
> * no network usage
> * no parameter copying
> We still use the RMI interfaces (e.g. RemoteExceptions), but the two
> above things are optimized. The second is of course optional since it
> breaks RMI semantics.
yes -- that's what I need. I've hoped EmbeddedTomcat provides
both of these things since I've thought it might be possible
But tell me exactly:
is the second feature implemented or not (you say above that it's
optional and it confuses)
I've wrote some tests: EJB creates huge String[100000+]
String[] getStrings(int arraySize, int stringLength)
and returns it to client (servlet running in EmbTomcat)
and I noticed long delay between the moment getStrings() did return
and client displayed result;
So please help me: need RMI when accessing EJB remotely and
DON'T want it when calling EJB from EmbTomcat
Or do I something wrong ? Special setup? Need to pray? ;)
Thanks.
---- ----
patrik.beno@{qbizm.com|inmail.sk} ICQ#98931498
-- --
Patrik Beno Qbizm technologies, Inc.
developer ... the art of internet.
------------------------------------------------------------------------
Kralovopolska 139 tel: +420 5 4124 2414
601 12 Brno, CZ http://www.qbizm.com fax: +420 5 4121 2696
