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.

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.

nick

[EMAIL PROTECTED] wrote:

On Fri, 24 Oct 2003, Lucas Nussbaum wrote:



I found some excellent docs on http://docs.jabber.org, but the site
seems to have closed down. Where are the docs now ? It would be great to
put them all back online somewhere.



Some docs are on http://jabberd.jabberstudio.org/1.4/docs/



I read that components can either be internal (does this mean that the
code is based heavily on jabberd's ?) or external (totally standalone
codebase ?).



Yes. Yes.




I think one of the advantages of an internal component is that it can
rely on xdb for data storage.



No. Any component can use the XDB services the Jabber server it connects to provides.

Internal components rely on the jabberd 1.4.x's codebase so they are
generally a bad idea. Use JCR, JECL or some other library to code external
components.



Is there a "component writing guide" ?



http://jabbermanual.jabberstudio.org/test/


It's not finished. It is currently undecided what way the docs are going.
Probably there'll be some Wiki-like pages on jabberdoc.org.

Regards
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev




_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev

Reply via email to