On Oct 25, 2003, at 1:00 AM, Nicholas Perez wrote:
Currently, writing components against the 1.4 codebase (externally or internally) is just a Bad Idea. Lots of not well thought out cruft has been growing like a slime mold over the past couple of years. Things have still not been standardized with regards to non-client, non-session oriented xmpp/JABBER(tm) entities. Some work has already been covered in various projects that seek to alter the way those types of entities interact, such as the PXR project (http://pxr.jabberstudio.org). I don't offer a solution to this problem, only a different point of view.
Internal components against 1.4 are certainly not a real bright idea, but external components are a known, proven way to add business logic to the 1.4 (or just about any server out there) codebase. There are lots of great components out there which use this mechanism.
We need to address this issue so we don't end up with a fragmented set of components that only work with one server. Ideally, there should be a protocol for entities not session manager connected.
Huh?
D.
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
