RMI/IIOP is a pretty optimized binary protocol so it seems that other
protocols may not solve your issue.
Using RESTful entities (Jersey in the case of GlassFish) and HTTP may
help with caching, streaming, etc...
SOAP Web Services with Metro do provide optimization like MTOM for
binary data and streaming for SOAP/HTTP.
Your solution might involve some sort of cache on the client side for
a better user experience.
As for updates, you probably should look into Grizzly Comet for HTTP-
based server-side notifications.
-Alexis
On Dec 26, 2008, at 19:14, glassfish_at_javadesktop.org wrote:
> Hello,
>
> In this moment my Eclipse RCP client 'talks' to the J2EE server
> through EJB remote interfaces but in some cases I need some large
> amount of data (one time only and updates later) on the client and
> this takes a long time, especially when over the internet.
>
> So I need to find another way of communicating, and I was thinking
> of switching to sockets, object streams and maybe compressed streams
> so that when the client application starts, it connects to the
> server, requests the initial data package, receives it and after
> that it listens for updates. The thing is that this is very slow
> also (without the compression now and probably this would not help
> much because it's serialized data anyway), so I need something else.
>
> Could someone help me on this?
>
> Thank you,
> [Message sent by forum member 'coboo' (coboo)]
>
> http://forums.java.net/jive/thread.jspa?messageID=323355
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>