Not to take away from all your good work - but do agree on the need to rename it See for example: http://www.beepcore.org/index.html Karim - is there any documentation/screen shots available without having to download and install the entire package ? Thanks Dave Cridland <dave@cridland.net> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On Wed Apr 25 16:32:08 2007, Karim Hamdan wrote: > I am glad to announce that my group has just released the beta > version of > our JME Jabber Library named "Beep Framework"... u can find the > project here > http://sourceforge.net/projects/beep/ and download it here > http://sourceforge.net/project/showfiles.php?group_id=183541 > > we r more than happy to receive ur feedback :D One bit of probably unwelcome feedback is that the name is very confusing - if I'd not seen it here, I'd have thought the protocol it implemented was BEEP, not XMPP. Naming your implementation of one asynchronous protocol carrying a payload of XML after another asynchronous protocl usually used with a payload of XML is not a terribly good idea, IMHO. Dave. -- Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade </blockquote>