[JDEV] Request for comments on system using jabber

Jens Alfke jens at mac.com
Fri May 25 12:13:47 CDT 2001


On Friday, May 25, 2001, at 09:26 AM, Thomas Charron wrote:

>     Now your talking about the improper use of a jabber client.

It's only "improper" based on the current server implementation. There's 
nothing architecturally wrong with it at all. In fact, it's 
architecturally superior because it's much more modular: it allows the 
bot to run on a separate machine from the server (anywhere on the 
Internet in fact), doesn't require any server reconfiguration, and will 
[barring scale issues] work with any conceivable Jabber server 
architecture, even ones that don't have the same internal design as the 
current one.

> Thats why that bot should actually be running off of a
> transport that is written specifically to handle that kind fo traffic.  
> Most
> likely storing the user data in some sort of in memory database, while
> persisting some of the data it requires for operation to more permenent
> storage.

Well, any server that plans to handle thousands of users ought to be 
written that way, since it sounds as though the current approach doesn't 
scale well at all. Then you wouldn't need to use a special transport for 
things like this.

Why not have the server use an external SQL database for storage? That 
way small installations that want to use free/open software can plug in 
mySQL, while large portals can use Oracle or Sybase or whatever.

—Jens
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1626 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20010525/c1ac4f45/attachment-0002.bin>


More information about the JDev mailing list