Many web applications are being implemented using XML for data transfer. The
advantages are that it provides a widely supported standardized form for the
data, which is especially useful if you want to allow other companies to
interface to your system directly (access your server system from their
applications without going through a browser, or implement your server interface
on their server systems). XML is great for interoperability.
The main drawback is that it's rather bloated for most applications, as compared
to some form of binary data transfer. With secure data transfer this problem is
likely to be emphasized because of the overhead of encryption/decryption.
You don't mention interoperability as a goal, so in response to your question
I'd recommend you use HTTP - this gives you easy access through firewalls and
security (with transparent HTTPS support in the browser environment), and for
reasonably large block transfers HTTP's performance is fine (there's a fairly
large per-request overhead, not much per-byte). It also gives you a simple and
widely supported server side interface with Servlets. No reason you have to
limit the transfer to stringed data, though - you can send any kind of binary
you want, just set the content type to some binary type so that the browser and
web server won't be confused.
Even if you did want to use XML, you'd probably still send the XML documents
back and forth with HTTP. XML is only a data format standard, it has no
transport capabilities built in.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
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
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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
