[jdev] client vs component

[Alexey Nezhdanov]

Joanne wrote:

>This is what I would like to do:
>
>1. I want to implement an external standalone application in C/C++ that communicates with the jabber server via TCP/IP sockets
>2. When the standalone app receives a message, it will block until it is finished processing the message. After it is done processing the message, it will process the next one, if any.
>3. I need the kind of flexibility that will allow this architecture to scale (i.e. so I can have several external standalone apps that basically listen for the same messages and process them as they come in.)
>
>Unfortunately, I'm a little confused as to how I should implement my standalone app. Should I write a client or a component? Can someone breifly explain the difference between a client and a component, and what the basic advantages/disadvantages are for both, and which one might be best for my needs?
>
Component:
You must have access to server config or at least obtain port/password 
pair from server administrator.
You will have no node - just domain (i.e. 'component.domain.org')

Client:
You must have login/password pair and access to port 5222(5223) of the 
server.
Your address will be in common form: node at domain.org

AFAIK there are no balancing mechanisms in jabber server so you will to 
write them yourself

--
Respectfully
Alexey Nezhdanov