Keep in mind that you can use a single port and send to a specific
destination. If you can identify the client specifically, then this
should be pretty easy. That would allow you to send messages only to the
clients that require the message. Creating a separate port for each
connection would not scale well (I know you said this wasn't so much of
an issue) and it could potentially be an administration nightmare.
With that said, there are a number of free servers out there. Oregano
(java-based) comes to mind. You had mentioned .NET, are you looking
specifically for a .NET server? I don't know of any offhand, but I
vaguely remember coming across one, maybe search on source forge. If you
are familiar with network programming, it is possible you could roll
your own if it has a specific need. What I mean is that it is not too
difficult to build something if a) you know how to build it (duh), and
b) the solution is very specific. The difficulty of writing a server
comes with all the options (plugins, clustering, highly customizable
messaging data, etc.).
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tracy
Spratt
Sent: Friday, November 04, 2005 2:44 PM
To: [email protected]
Subject: [Flashcoders] Need advice on XMLSocket architecture
Hello, I'm a regular on the flexcoders list, where it was suggested
that I ask my question over here. Any advice will be welcome!
I have 100 fixed, identifiable clients running a Flex 1.5 app on an
intranet. A Dot.Net integration tier maintains individual states for
each client. The integration tier talks asynchronously to third party
apps over async tcp sockets and even mail transport. I had planned on a
leisurely polling setup to get the clients updated with changes in
state, but I now have a requirement for an update with minimum latency.
The messaging between clients and server is very low frequency (a few
clients updated per minute) and very low message size (a few k per
update).
I am now looking at a true "push" connection using XMLSockets. I see
two approaches:
On would be to have a separate port connection for each client with each
client only getting their messages, the other would be a single port,
where all clients would get all messages, and ignore those that were not
theirs.
In my case performance, reliability and simplicity are most important,
and scalability not so much an issue.
Any suggestions, experiences, resources would be appreciated!!
Tracy
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
