Thanks. I'm project managing the design and
development of a commercial application, that will use Jabber as a
base. I'm trying to work up a an rough estimate of the development
costs for the financial guys. I've read through the first half of "Programming Jabber" and suspect that other implementations of the Jabber server must be somewhat similar in architecture? For example, allowing components to connect to the backbone using library load, TCP, and STDIO connections. I think most of the application can be handled by the standard Jabber components, with most of the specialized functionality in the client. However, I will need to plug in several custom server components. I'm basically working at the block-diagram level at this point... just trying to scope out the project. As far as requirements for the server are concerned, what I'm mainly concerned about is stability and scalability, as this application must potentially support lots of simultaneous users. The actual number will depend on the market, so we need to be able to start small and grow arbitrarily large. I'm a bit worried about that requirement, to be honest. Anyway, any thoughts much appreciated. Brgds: John Hal Rottenberg wrote: On 9/11/06, Matthias Wimmer <[EMAIL PROTECTED]> wrote: --
Marketing for Online Collectible Dealers Identry, LLC 249 Lenox Road Huntington Station, NY 11746 Phone: 631.546.5079 Fax: 631.980.4262 Email: [EMAIL PROTECTED] Web: www.identry.com Members: ASDA, APS, ANA, PSA |
begin:vcard fn:John Almberg n:Almberg;John org:Identry, LLC adr:;;249 Lenox Road;Huntington Station;NY;11746;USA email;internet:[EMAIL PROTECTED] title:Managing Partner tel;work:631.546.5079 tel;fax:631.980.4262 x-mozilla-html:FALSE url:http://www.identry.com version:2.1 end:vcard