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

[aquarium]

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.

[schweini]

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.

[zengargoyle]

indeed... you'll be able to interact with your agents (servers) just like you would a good friend.

[e-mail] says yo! 192.168.254.12 just scanned me!

[e-mail] says you hear that Q? block that biatch.

[e-mail] says right away sir!

[e-mail] says my printer stopped working, what gives?

[e-mail] says what's it's name/ip?

[e-mail] says printer4.sub.dom

/msg Q wha? printer4
[e-mail] says hrm, printer4 eh?
  host: printer4
  status: disabled (expired account 12345)
/msg Q tell luser wha

[e-mail] says somebody forgot to pay $$ do you have a new account?

[e-mail] says 54321

/msg Q mod printer4 account 54321
[e-mail] says mod printer4 eh?
  host: printer4
  status: nominal

[e-mail] says fixed u luser biatch

[e-mail] says block 192.168.254.1 active
...

then i just have to replace myself with a bot and go on a long vacation.

[schweini]

actually, this is kinda what i'm doing!
seriously! i even got some PHBs asking my system in plaintext about sales in stores, and they like it!
now, where did that ELIZA code go.... ;-)