[JDEV] Concern regarding transport overload..
tcharron at nermail.ups.com
Wed Mar 31 10:29:08 CST 1999
> From: owner-jdev at jabber.org [mailto:owner-jdev at jabber.org]On Behalf Of
> Subject: Re: [JDEV] Concern regarding transport overload..
> I'd like to actually have a completely different codebase(sharing the
> common libs of course) to handle the special ISP server, one that is lean
> and requires no setup/config, and that is limited in functionality
> available. If they hit a point where they want more functionality,
> upgrade, but this gives them an easy way to try it out and make it
> available NOW without worry.
I can provide this as an NT service with little problem.. ot right NOW,
mind you, but it'd be relitivly simple..
> Ooohhh... I see a minor confusion here :)
Yep, there was.. ;-P
> A 'transport' is quite different than a 'module'. The transport is a
> completely seperate 'server' process that understands the server <->
> server Jabber protocol and can translate to another messaging service OR
> serve a special function/purpose.
Ahh, see, in the past we've always refered to it as 'In A Transport', so I
imagined several DIFFERENT transports, one for each type.. ;-P
United Parcel Service
"Moving at the speed of a T3 Trunk Line!"
More information about the JDev