On Sep-25, Matthew Sachs wrote: > On Sep 25, 2004, at 22:50, Steve Fink wrote: > > >The working name is Net::IMClient for the general module, and > >Net::IMClient::Jabber for the jabber support. I suppose I could use > >'XMPP' rather than 'Jabber' in the name, but apart from that, is this a > >good space? 'IMClient' seems a bit clunky, and oddly is normally (but > >not always) used to implement daemons. The "client" in the name is > >because they are always clients in the instant messaging protocol > >sense, > >which is independent from the sense of the functionality they > >implement. > > I was planning on Net::IM when I started trying to design such a beast > a few years ago. That project never got off the ground, you're welcome > to use that name if you'd ilke. You may also be interested in > http://cvs.sourceforge.net/viewcvs.py/*checkout*/perl-net-im/perl-net- > im/doc/spec.pod?rev=1.2
Ah, I see what your problem was: you were actually trying to do things *right*. I, on the other hand, whipped up my implementation as a quick hack to fix an unrelated problem at my day job. In fact, I did it completely backwards -- the inheritance tree is upside-down, for instance. But as a result, I got it working quickly and have been using it successfully for the last few months. Now I want to publish it on CPAN, so I need to go back and fix the mess, thereby making it much closer to what you spec'ed out. Thank you for the offer of the namespace. I think the Net:: toplevel probably fits your design better than it will ever fit mine. (Especially since I'll probably never pay more than lip service to protocol-neutrality.) I suppose I could put the protocol adapters under Net::IM and the application framework under something else.
