>
>I chose to adapt the email client I've been working on to create cards rather than
>store text files. I can't see the point. I can see the dissadvantages - can't search,
>slightly slower access, messy file structure, but no real advantages.
Originally I was storing the mail as custom props in a second stack but it kept
growing and growing and by the time it was 4M it became to slow at sorting things.
Besides if the stack is gone all the mail is gone. Creating a mechanism for periodic
archiving is probably easier with a bunch of files. That's not to say that this method
is perfect.
>
>The strategy i was thinking of taking was to archive stuff over xmonths old and junk
>as either text files of stacks (not sure yet) and keep a reasonable size of stack in
>memory (spitting off chunks when it needs to slim down) - what do you think?
>
> Had a quick look at the scripts and prefer the syntax:
>
> " open socket targetserver with message sockopen"
>
>as it's neater, and you can do other stuff in case of a network delay. What do you
>think about altering the scripts to handle the conversation with this technique?
Yes, I'll look into it. The thing is that you don't really want to do other stuff
unless you have an open connection (that was my thinking).
>
Regards, Andu
_______________________
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
