On Tuesday 09 September 2003 03:34 pm, Autrijus Tang wrote: > 在 ?G, 2003-09-09 01:54, Perl Authors Upload Server 寫道： > > The following module was proposed for inclusion in the Module List: > > modid: Net::BeepLite > > DSLIP: bdpOl > > description: lightweight BEEP framework > > userid: DBLACKA (David Blacka) > > chapterid: 5 (Networking_Devices_IPC) > > communities: > > [EMAIL PROTECTED] > > This is a BEEP protocol framework (RFC 3080, 3081), and, as such, > > it is a bit like other internet protocol frameworks (Net::FTP, > > Net::DNS, etc.). > > Following the example of SOAP::Lite, wouldn't BEEP::Lite of > Net::BEEP::Lite be more intuitive? :-)
I would be uncomfortable suggesting the new top-level namespace of BEEP, seeing as there is only one module for it. A closer analog to this module might be HTTP::Lite, rather than SOAP::Lite. Net::BEEP::Lite would be fine, however. Although BEEP has been defined for 2 years, this is the first non-vaporware perl implementation of it that I'm aware of. I would hope that at some point a more comprehensive implementation of BEEP (one that supported the complex peer-to-peer and channel multiplexing) to be implemented at some point. It would seem to make more sense to call that Net::BEEP rather than BEEP for BEEP::Full or something like that. -- David Blacka <[EMAIL PROTECTED]> Sr. Engineer Verisign Applied Research
