Very Computer

1. Serialization of objects stored persistently (and use of the transient modifier) sent to an applet

Forwarding on below email to this group as well...knowing that the diamond
in the rough could be here too...

Hi all,

Have couple of questions for the ObjectStore and Pattern experts out there.
So here is a detailed account of my current situation (in psuedo-pattern
catalogue detail).

Problem:
How to transfer over a persistent object via serialization but without
recursively serializing particular referred objects within the persistent
object (i.e., using transient modifier) so as not to inundate network
traffic to the end client where the applet will receive this serialized
object.

Participants:
* Applet (end client)
 - awaiting transfer of serialized object.
 - will make necessary calls for new serialized objects

* Serializable object
 - lightweight when serialized so as not to inundate traffic if associated
  object has thousands of recursive objects underneath it (i.e., this
  object is a Composite type object).
 - stored in the ObjectStore database (including all its children objects)

* ObjectStore (OO Database)
 - store the Serializable object and all its object references (recursively
of course).

Environment:
ObjectStore 5.1 (OSJI 1.3) running on Windows NT Workstation 4.0

Sample Code:
/**
 * Simple test class demonstrating what I want to do but not sure if it will
 * achieve my objectives.
 */
import COM.odi.util.*;

public class Test implements Serializable {
 Test() {
 }

 private transient OSVector list;

 //yadda, yadda...other fields and methods of interest that we do want
 //serialized

Questions:
1. First (for the ObjectStore experts), will the transient list object be
properly stored into ObjectStore?  Basically, I want to have Test class be
persistent capable class.  And I DO want the associated list object to be
stored in the database as well.

2. Second (for Patterns or ObjectStore experts), is this the best way to do
this?  A colleague of mine mentioned something about creating a Proxy type
class that I transfer down to the applet.  Would this be a better solution?
Any other ideas about how to transfer over a persistent object via
serialization but without killing the network traffic to the end client
where the applet will receive it?

Many thanks in advance,

J.D.

--
J.D. Fagan
2Bridge Software

2. US-NY-NYC: C/C++/Sybase, major bank

3. Problem with Applet Servlet communication

4. Jobs In SQL Server

5. Servlet and Applet Communication

6. "Table must be declared" in procedure?

7. applet to servlet communication

8. Delphi 1.0/Access 1.1 via ODBC

9. http communication between applet and servlet

10. Communication Servlet-Applet

11. Applet-Servlet Communications.

12. http communication between applet and servlet

13. Applet-Servlet communications