dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.2.6
postmodern has quit [Quit: Leaving]
Azure|dc has joined #cinch
Azure has quit [Ping timeout: 244 seconds]
Rickmasta has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Rickmasta has joined #cinch
apt-get has joined #cinch
Rickmasta has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
apt-get has quit [Ping timeout: 252 seconds]
apt-get has joined #cinch
Zackio has quit [Read error: Connection reset by peer]
Zackio has joined #cinch
Zackio has quit [Read error: Connection reset by peer]
Azure|dc has quit [Ping timeout: 246 seconds]
apt-get_ has joined #cinch
apt-get has quit [Ping timeout: 246 seconds]
apt-get_ is now known as apt-get
<greenbigfrog>
is it possible that I listen to a message on server A and then respond something on Server B? Basicaly connecting to 2 servers? (This could be usefull for linking channels and so on...)
<greenbigfrog>
dominikh: ping
<dominikh>
a) if you run two instances of Cinch and have them communicate, sure b) please don't always ping me. this is a low traffic channel, there's no need for pings, I'll take a look when I have the time
<greenbigfrog>
ok
<greenbigfrog>
how would that communication look like?
<dominikh>
method calls.
<greenbigfrog>
ok... thanks
<greenbigfrog>
can you give a link to a example please? (I don't exactly understand how to...)
<dominikh>
do you know Ruby?
<greenbigfrog>
yes... but not that much
<dominikh>
sorry, but I'm otherwise occupied.
Azure has joined #cinch
<apt-get>
greenbigfrog: 1) send a message from bot_a to bot_b on server A when an event happens there
<apt-get>
bot_b, after receiving that message, will proceed to do whatever on server B
<apt-get>
or at least that's how I'd assume it would work