Steve Buonincontri wrote:
> Sorry,
>
> I need to send this question again:
> ###########################################################
>
> While we are on the subject of XML.
>
> Is XML a good solution for moving JTable data from server to client and from
> client to server?
>
> when moving large object data like a table - we need performance, we need the
> data to get moved through a firewall and we need it secure. Sometimes these
> blocks can get large (~5000 records etc.)
>
> So, I ask the question XML, RMI, HTTP (send stringed data), RAW SOCKET, or
> URLConnection, ........
>
> What is the best way to move large tables to a browser these days - when the
> goal is to get performance, security and reliability?
>
> Does it make sense to be moving an XML doc back and forth and managing the
> communication through this XML document?
>
> - steveb
>
If performance is your primary goal, you want the approach that minimizes the
number of bytes sent across the wire, balanced by the effort required to program
it. I would suggest you add a couple of options to your list that try to strike
a reasonable balance:
* Use HTTP, but send a stream of serialized Java objects
representing the results.
* Use HTTP, but send the results in a structure like the
CachedRowSet implementation you can get at JavaSoft's
web site.
Either of these has some overhead (versus sending just stringified data), but
they are very easy to program for. RMI uses serialized objects underneath, but
can cause you grief when you have to cross firewalls.
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
