yea - i did a RPC-via-mysql prototype once, too, but somehow it felt clumsy, since i had a cronjob checking whether there was anything to do since the last run.
i'm looking for the most generic/extenable/scalable connection-type out there, that's why i'm looking at jabber (AFAIK it was designed with these goals (but a different application in) mind)
do you really think that jabber is less reliable than some other form of inter-box communication? as far as i can see, messages either arrive or they don't (i doubt unterminated XML is marked as 'received'), and the risk of a corrupted message seems negiable, i hope.
am i missing something? | [reply] |
database like progress has triggers...so when a table gets new data it will spring your procedure into life. good thing about databases is data integrity...if you want to have constraints on a field (say command name), then once you setup your database you don't need extra code...you want to fish out a command used ages ago, no prob, just look in the logs/history table...you want to have distributed architecture with a redundant (live) server, done. If you want no frills RPC then use RPC module, why bother with jabber bloat. no offense to jabber, it's good for what it was made for.
| [reply] |
sure sounds neat..only problem being (ahem) mysql's extensive support for triggers ;-)
very TMTOWTDI way to do it, too...but i'll just be stubborn as hell and stick to jabber (did some testings i rather liked).
it does have the enormous advantage of making debugging a lot easier, too...
thanks, again.
| [reply] |