[00:35] *** mercutio has joined #arpnetworks [05:45] *** heavysixer has joined #arpnetworks [05:45] *** ChanServ sets mode: +o heavysixer [06:01] *** heavysixer has quit IRC (Quit: heavysixer) [06:43] *** heavysixer has joined #arpnetworks [06:44] *** ChanServ sets mode: +o heavysixer [06:58] *** heavysixer has quit IRC (Ping timeout: 245 seconds) [08:13] man, zeromq is some neat stuff [08:14] truth [08:59] *** eryc_ is now known as eryc [09:11] *** eryc has quit IRC (Changing host) [09:11] *** eryc has joined #arpnetworks [13:11] http://i.imgur.com/haspR.jpg [13:34] wow [13:38] up_the_irons: we're looking at replacing xmpp with zeromq on v 3.0 of our appstack. [13:38] up_the_irons: what are you using it for? [13:51] rabbitmq is also hawt [14:09] *** heavysixer has joined #arpnetworks [14:09] *** ChanServ sets mode: +o heavysixer [14:11] jpalmer: I'm guessing you're not using XMPP for simply chatting then? (Not that you couldn't build an IM service with a 0MQ transport...) [14:13] we're doing a LOT with xmpp, that it wasn't really designed for, or good at. [14:14] heh [14:15] I've used xmpp for intra-server message passing in the past (5+ years ago). it did well enough. Was relatively small scale though and I would definitely jump on 0MQ now. [14:15] I will say that XMPP is nothing if not extensible though [14:17] we're using it in hospitals. for messaging, voip session setup, delivering critical alarms to nurses.. etc. oh, and we're doing it over (usually) poor quality wifi.. so there are lots of drops/disconnects. [14:21] at least xmpp retransmits upon reconnect! [14:22] well, not well in our scenario. if the phone is unavailable, we send it as an apple push, and need to remove it from the queue [15:07] does xmpp support "guaranteed" delivery? not sure if that's the right word to describe it... [15:07] basically, retry until it gets through [15:08] *** heavysixer has quit IRC (Quit: heavysixer) [15:13] jlgaddis: I'm not sure, but I know it supports delivery receipt, so I'm sure there must be some implementation/addon/etc that would retry . [15:13] (As far as I know, most setups will store and and pass it along) [15:14] yeah, delivery receipt is basically what i meant... i was thinking it does, but it's been a few years since i used jabber (previous job) [15:19] its supposed to, but some im apps screw it up I think, don't rely on blackberry gtalk client, it shows online at google and online at blackberry at times, yet manually disconnecting and reconnecting is the only way to get it to start receving messages sent from elsewhere or have others receive messages sent [15:20] heh, that could (in theory) be fixed at the server side [15:20] If the server would reach out, ping, etc [15:21] Not guaranteed but an option [15:21] when running a jabber server, I'd notice I could send a message to an offline contact, disconnect my client, connect to the offline account, and receive the message. I was impressed. [15:21] lol [15:22] that reminds me, toddf, and i now remember the answer to my own question [15:22] Anyhow, the client must ack every message received from the server. Hence, the server will know whether it was delivered, and will report it as such back to the sender. [15:23] i remember similar things happening when we had a jabber server (receiving messages from when i was offline) [15:23] *** Ehtyar has joined #arpnetworks [18:37] *** heavysixer has joined #arpnetworks [18:37] *** ChanServ sets mode: +o heavysixer [18:59] *** heavysixer has quit IRC (Quit: heavysixer) [19:00] *** heavysixer has joined #arpnetworks [19:00] *** ChanServ sets mode: +o heavysixer [19:21] *** DiaboliK has quit IRC (Ping timeout: 256 seconds) [19:28] *** DiaboliK has joined #arpnetworks [19:45] *** dzup has joined #arpnetworks [20:06] *** heavysixer has quit IRC (Quit: heavysixer) [21:12] *** E1ven has joined #arpnetworks [21:49] *** E1ven has quit IRC (Quit: Computer has gone to sleep.) [22:36] *** dzup has quit IRC (Ping timeout: 245 seconds) [23:46] *** Ehtyar has quit IRC (Quit: Don't follow me)