> One thing we're experimenting with, especially for data which is represented by a
>complex graph of related objects, is to send the entire state of the graph to the
>client as an XML document. The client then interacts with the local representation
>until it needs some logic that's on the server. It's not yet clear to me whether
>this will work - the overhead may cancel any gain. Time will tell.
I've had some success with this. Particularly for large graphs. Also, try
transporting the stateof the graph as zipped XML. XML of this sort typically has lots
of redundant features, so it compresses like crazy. Particularly when you're
bandwidth-limited, it's well worth looking into.
Ed Smierciak
Enduden Consulting
>
>
> Steve Demuth
>
> Artemis Alliance, Inc. An Inprise Premier Partner
> 289 East Fifth St, Suite 211
> St. Paul, MN 55101 [EMAIL PROTECTED]
> 651-227-7172 or 319-382-0593
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
