-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Charles wrote: > On Fri, Mar 21, 2008 at 2:33 AM, Micah Cowan <[EMAIL PROTECTED]> wrote: >> The intent is that all the writer operations would take virtually no >> time at all. The sidb_read function should take at most O(N log N) time >> on the size of the SIDB file, and should take less than a second under >> normal circumstances on typical machines > > What encoding will this session database file use?
I was thinking ASCII, probably; with filenames and URIs percent-encoded as necessary. Other values should probably follow suit (or else use MIME's mechanisms for character encoding within headers, where that's appropriate). Probably direct byte values for non-ASCII value would be accepted (but not generated), and assumed where possible to be appropriate for their context, except when there's a danger of Wget sending malformed data. NUL should be disallowed, though, because it's probably too much work to support those in our current code (they would be necessary to some character encodings if represented directly). The idea is that it should be as absolutely easy as possible to manually edit. YAML uses UTF-8; I'm beginning to think YAML may not be what we want, though, given that the definition for a given entry may be interposed with defining content for other entries; I don't want to kludge that by suffixing the names or something. I'll have to look more into YAML to see how doable that is. If we did end up using YAML, then obviously we wouldn't accept arbitrary byte valus: it'd be UTF-8 only. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH4+zt7M8hyUobTrERAp9RAJ49fyIroAnskn1Iyo0UjI61DnrdNwCgkV85 +1+nO0xd1rr4zQZKGHYuhDM= =sMQq -----END PGP SIGNATURE-----
