-----BEGIN PGP SIGNED MESSAGE-----
Daniel Kinzler schrieb:
Marcin Cieslak schrieb:
> Daniel Kinzler wrote:
>> Marcin Cieslak schrieb:
>> Hm... I suppose the "master" copy of the messages in the
>> should indeed be maintained by the author, as
a flat file in the
>> the "live" messages could be pulled
from a db that is updated
Maybe from there they could be exported again into the
Are you sure you want to query your messages "live" on the
why not? that's relatively cheap.
If you download them once and store them in some
kind of a hash table
you need to tell the application somehow to refresh the hashtable.
If you have a persistent application, yes. it could simply discard the hash
after an hour or so. But cgi scripts and php applications are restarted for
every request anyway.
Not much different from need to go via "svn
Sure it's different: it happens automatically. Which is somethign i
to happen with code.
In any case: applications should load messages from a database or flat
every request or at least periodically every few
hours. Messages could
automatically from betawiki. The next step would then
be to get such
into the respective tool's repository. That's
the last step, really.
Toolserver-l mailing list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----