[14:53:31] --- demmer@jabber.org has joined
[15:15:13] --- sftcd@jabber.org has joined
[15:15:14] --- sftcd@jabber.org has left
[15:16:02] --- sftcd@jabber.org has joined
[15:16:03] --- sftcd@jabber.org has left
[15:17:15] --- sftcd@jabber.org has joined
[15:17:15] --- sftcd@jabber.org has left
[15:18:57] --- sftcd@jabber.org has joined
[15:18:57] --- sftcd@jabber.org has left
[15:21:39] --- sftcd@jabber.org has joined
[15:21:39] --- sftcd@jabber.org has left
[15:25:26] --- sftcd@jabber.org has joined
[15:25:26] --- sftcd@jabber.org has left
[15:25:38] --- sftcd@jabber.org has joined
[15:25:54] <sftcd@jabber.org> hey - just me here today?
[15:26:22] <demmer@jabber.org> me too
[15:26:45] <sftcd@jabber.org> complicated stuff eh
[15:26:51] <demmer@jabber.org> yes
[15:27:25] <sftcd@jabber.org> did we ever figure out how multi-cast and odd routing schemes like flooding relate?
[15:32:33] <sftcd@jabber.org> hey - got my answer
[15:32:39] <demmer@jabber.org> yep
[15:33:34] <demmer@jabber.org> as you maybe can tell from my comment -- i have a personal bias that many of these issues are hard to determine by just writing a spec, and that you figure out the real problems by trying to implement something, then write about it later
[15:49:48] <sftcd@jabber.org> sounds sensbile to me - I'm gonna bail now and go for dinner - you can announce my absence if I'm needed:-)
[15:49:55] <demmer@jabber.org> ok
[15:49:59] <demmer@jabber.org> signing off
[15:50:00] --- demmer@jabber.org has left
[15:50:05] <sftcd@jabber.org> bye
[15:50:25] --- sftcd@jabber.org has left