On 10/8/06, Daniel Henninger <[EMAIL PROTECTED]> wrote: > Hi Norman! While it is a lot more work, most of that work you can > probably steal from PyAIMt/ICQt/MSNt. (maybe, forget how much if it > is twisted dependent) Anyway, the single file will end up becoming a > problem quick on some systems. Some Solaris's have cap of 2 gig per > single file, for example. Keep in mind that once you start doing it > in multiple files you'll run into the same problems we did, where you > end up needing to create different subdirectories. (too many files > in one directory causes problems for some systems... I think this > applies to all systems just some run into the limit quicker than others)
Yea, part of the reason why I want to get the avatars out of the data file (size + efficiency), and keep everything else where it is (no more code changes). On 10/8/06, Will Tatam <[EMAIL PROTECTED]> wrote: > Given this is how the PyMSNt transport works, and seams to work > effectively already, this seams the most logical thing to do and in fact > i'm amazed that this change wasn't made to all the Py*t transports at > the same time because there are three different code maintainers? -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Sun Oct 8 18:49:13 2006 From: [EMAIL PROTECTED] (Daniel) Date: Sun Oct 8 18:49:18 2006 Subject: [py-transports] PyYIMt not saving settings/registration? In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> >> Interestingly enough, I grabbed that tool and ran my user database >> through it. I get *one* user listed with his username, password and >> subscription status. The file is about 750KB, so I'm pretty sure >> there's more data in there (not to mention my being able to look >> through it for occurrences of my username and such). So do you think >> ti sounds like the file is corrupt? Maybe I should just trash it and >> start it over. Has the format of the file changed any since the last >> release? > > I doubt the file is corrupt, just that the 'shelve'/'pickle' formats > are probably not great. You probably find that they don't zero > memory, and use lazy storage, etc. Not to be rude or anything, but if you suspect the code you're using to handle the file formats isn't very great, why not use something that's more mature and reliable? I don't know anything about the shelve/pickle formats, but, I'm sure there are other things out there that'd work well. Just my $0.02. :) Daniel [EMAIL PROTECTED]
