Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Re: using jabber for RPC or inter-server-communication

by aquarium (Curate)
on Jul 29, 2003 at 03:35 UTC ( #278714=note: print w/replies, xml ) Need Help??


in reply to using jabber for RPC or inter-server-communication

you could use a range of client/servers, e.g. mysql database or postgres if you want triggers, RPC, email, FTP, news, etc. You should think about the characteristics of the connection you want and try to match that to an existing protocol (for the sake of re-use and not having to write your own client/server). That crucial answer will steer you in a particular direction. I'm not sure that a chat server/client is particularly well suited to the transmission of commands, as on a chat session it may not be a big deal if a character gets lost here or there--commands and their parameters must be 100% delivered and executed or 0%. oh well, that's my addition to your salsa.
  • Comment on Re: using jabber for RPC or inter-server-communication

Replies are listed 'Best First'.
Re: Re: using jabber for RPC or inter-server-communication
by schweini (Friar) on Jul 29, 2003 at 08:16 UTC
    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?
      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.
        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.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://278714]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (8)
As of 2020-11-30 13:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?