[DGD]serialisation/deserialisation of mixed data.

[Jason Cone]

> -----Original Message-----
> From: dgd-admin at list.imaginary.com
> [mailto:dgd-admin at list.imaginary.com]On Behalf Of
> balduin at uni-paderborn.de
> Sent: Thursday, April 29, 1999 4:22 AM
> To: dgd at list.imaginary.com
> Subject: Re: [DGD]serialisation/deserialisation of mixed data.
>
> [...]
> objects.  If I use a state-dump reboot won't help a lot to decrease this
> number and i'd be limited to about 10k Documents or even less, if I assume
> that modern html pages consist of a lot of subdocuments e.g. pictures.
> This is a lot for a single class, but even the document server of our
> workgroup at my university has about 10k documents.
> [...]
>
> [And from an earlier post...]
> system. One part of the system will be (is) a html server and to achieve
> link consistency every single bitmap has to be an object.
> [...]

I guess I'm having a hard time understanding why documents, bitmaps, and
other served entities need be an actual objects.  To me, that would
significantly slow down the serving process as the object would need to be
converted to the protocol's expected stream.  Am I missing something?  I
agree, though, if you were expecting to max out your object count, an SQL
solution might be called for.  Could you explain your motivation for using
objects to encapsulate everything?

--
  Jason Cone
  Sr. Software Developer
  Usability Sciences Corporation
  jcone at usabilitysciences.com



List config page:  http://list.imaginary.com/mailman/listinfo/dgd