-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
You might do best to split the data onto separate stacks and save them independently. When the data is needed, you can retrieve it from the appropriate stack; when you change it, you copy it back to the data stack it belongs in and, at an appropriate time, save the data stack.
On Jan 26, 2005, at 10:53 AM, Lynch, Jonathan wrote:
Saving a large stack can be time consuming - especially across a network.
Would it be possible to have some sort of write-to-file scheme that just
changes the stored data for single card, but not the entire stack?
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
- ----------------------------------------------------------- Frank D. Engel, Jr. <[EMAIL PROTECTED]>
$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.
$
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFB98jX7aqtWrR9cZoRAs2aAJ41DXwnIiTcRjqR4Ltdm3ynsH9/rwCfd++B zMnpD8u2MrcB2libE7qesno= =4OQu -----END PGP SIGNATURE-----
___________________________________________________________ $0 Web Hosting with up to 120MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
