well, i've implemented the php lib for use at the toolserver mostly. i'll poke nikerabbit obout the export again. basically, i'll try to use this for my own tools, and tell you about how it works out.
however, i don't have much time for this right now, i have pretty much sold out all my computer hours. so it may take a while until it gets done. if you want to go ahead and play with it yourself, I can provide the code I have so far.
-- daniel
Luxo schrieb:
Any news?
Daniel Kinzler schrieb:
Marcin Cieslak schrieb:
Daniel Kinzler wrote:
Marcin Cieslak schrieb: Hm... I suppose the "master" copy of the messages in the "primary"
language
should indeed be maintained by the author, as a flat file in the
repository. But
the "live" messages could be pulled from a db that is updated
automatically.
Maybe from there they could be exported again into the tools.
Are you sure you want to query your messages "live" on the database every time?
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 up".
Sure it's different: it happens automatically. Which is somethign i
don't want
to happen with code.
In any case: applications should load messages from a database or flat
file, on
every request or at least periodically every few hours. Messages could
be pulled
automatically from betawiki. The next step would then be to get such
messages
into the respective tool's repository. That's the last step, really.
-- daniel
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
_______________________________________________ Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l