In Java, for example, objects aren't serialized as an object, just their class name and instance data is serialized. Then on the receiving end, a class of the same type is instnatiated, and the serialized instance data is injected into the new instnace. This has a couple consequences: 1) you don't need to worry about sending objects, just data, and 2) you must have all serialized classes on BOTH sides of the transaction.
cheers, barneyb On Wed, 16 Feb 2005 16:40:06 -0500, Calvin Ward <[EMAIL PROTECTED]> wrote: > Wonder how bloated object serialization would be... > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:195102 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
