[00:45:18] ** _jpl_ has joined us
[00:45:18] ** jack-e|away has joined us
[06:54:53] ** vlado_ has joined us
[10:10:55] ** vlado_ has joined us
[11:00:32] ** Maniac has joined us
[18:58:54] ** _jpl_ has joined us
[20:41:27] <_jpl_> shhh, it's far too noisy in this channel.
[21:15:37] <Maniac> YAAAAAAHOOOOOOOO!
[21:15:39] <Maniac> see i yelled
[21:15:49] <Maniac> _jpl_,  what is the advantage of junction?
[21:16:23] <Maniac> and to implement a proper credential checker i just implement ICredentialChecker?
[21:39:00] * Maniac wonders if he needs to yell ;)]
[22:14:10] <_jpl_> ICredentialChecker isn't implemented yet, since I haven't worked up the Twisted interface support yet.
[22:14:16] <_jpl_> But that's the idea.
[22:14:48] <_jpl_> The advantage of Junction is that you have a single simple utility which handles distributed pub/sub and request/respond actions for you.
[22:17:01] <_jpl_> Currently it only supports Twisted PB, but the idea is to extend it to support multiple "endpoint" types (IRC, Jabber, CORBA, PyRO, etc.).  You'd then be able to hook it up to any number of those endpoints at the configuration level without the application ever needing to worry about the underlying communication plumbing.
[22:19:13] <_jpl_> So in a ZConfig file (latest Junction code is configurable through ZConfig; this isn't checked into tigris.org yet) you'd setup all the endpoints, subscriptions and other message routing info, and then any publications (for example) within the application would get sent to the right place, be it through PB, Jabber, or what have you.
[22:41:24] <Maniac> so when does it get checked in :P ?
[22:47:10] <_jpl_> Done
[22:55:16] * _jpl_ goes away for the night
[23:06:42] <Maniac> cool
[23:06:43] * Maniac goes to read