RE: What do you like about your i? Was->RE: Saving the Systemi:FightRather Than Switch

stream files handle MP3s and other large binary objects well enough.

In a networking world, where objects have to be convertable to and from
string form so they can be sent from here to there, the OS has to support
biggee sized strings.  Teraspace I guess is the answer, but I have my
doubts.

In a servlet engine scenario where you are serializing objects to persist
across whatever failures you are trying to avoid you would still do paging
of data sets (i.e. if you had a 10,000 record file you wouldn't load it into
a data grid and let Java/.NET page through the data set in memory, instead
you would use SQL keywords like LIMIT and the like).

The same would be true in my mind where you are doing SOAP web services
(which is where I am guessing you are coming from).  You simply wouldn't try
to send thousands of records through a pipe that was meant for program to
program communication and NOT meant for DB to DB communication (i.e.
replication, mass transfer) - because those SOAP methods are inevitably
consuming mass amounts of memory.  Now if mass XML/SOAP was necessary you
could go the attachment route and then the mechanisms on either end know to
deal with it more as a file than inner program memory.  Hope I made sense
there.

Aaron Bartell