the same thing that happened with all the jig mailing lists might happen? e.g. components list would be dead?
On Fri, 2002-06-07 at 12:26, Dave wrote: > Maybe we should setup a mailing list for components? We already have > the jdev list for clients (primarily for client-concerned issues, to > be more precise) and the jabberd list for the server. Why shouldn't we > have a list for transports/agents/gateways/components? > > Just a couple of pennies, > Dave Cohen <[EMAIL PROTECTED]> > > > Justin Kirby wrote: > > > > In an attempt to provide a central place to babble about components, I > > have put up a page on theo's wikki: > > http://www.theoretic.com/index.cgi?Components_HOWTO > > > > So for all you component experts out there, please help newbies out by > > adding comments/suggestions, battles fought and won or lost, etc... > > > > On Thu, 2002-06-06 at 13:29, Nicholas Perez wrote: > > > It is very very little, but enough to get you started. > > > > > > http://docs.jabber.org/general/html/component-intro.html > > > > > > > > > Andy Beetz wrote: > > > > Is there any documentation available for writing internal components? > > > > > > > > Thanks in advance > > > > > > > > | > > > > > > > > >--------------------------------------------------------------------------------------------------------------- > > > > Clearswift monitors, controls and protects all its messaging traffic in > > > > compliance with its corporate email policy using Clearswift products. > > > > Find out more about Clearswift, its solutions and services at > > > > www.clearswift.com. > > > > >*********************************************************************************** > > > > This communication is confidential and may contain privileged > > > > information intended solely for the named addressee(s). It may not > > > > be used or disclosed except for the purpose for which it has been > > > > sent. If you are not the intended recipient, you must not copy, > > > > distribute or take any action in reliance on it. Unless expressly stated, > > > > opinions in this message are those of the individual sender and not of > > > > Clearswift. If you have received this communication in error, please > > > > notify Clearswift by emailing [EMAIL PROTECTED] quoting the > > > > sender and delete the message and any attached documents. Clearswift > > > > accepts no liability or responsibility for any onward transmission or use of > > > > emails and attachments having left the Clearswift domain. > > > > > > > > This footnote confirms that this email message has been swept by > > > > MIMEsweeper for Content Security threats, including computer viruses. > > > > | > > > > > > > > > -- > > > Nick > > > > > > JabminRPC Developer > > > JabberSMTP Developer > > > ChatBot's B1tch > > > > > > > > > _______________________________________________ > > > jdev mailing list > > > [EMAIL PROTECTED] > > > http://mailman.jabber.org/listinfo/jdev > > > > -- > > JID: [EMAIL PROTECTED] > > > > ,/^^^^\, > > / \\. > > /| > > /| /''\___/ > > /''\__/ |/ > > /''\__/ |/ > > \\ ./ > > `\..../ > > > > http://www.openaether.org > > > > _______________________________________________ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev -- JID: [EMAIL PROTECTED] ,/^^^^\, / \\. /| /| /''\___/ /''\__/ |/ /''\__/ |/ \\ ./ `\..../ http://www.openaether.org _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
