I have 100 fixed 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 size (a few k per update).
Since I have been unsuccessful at getting a “blocking” http service call working in dot.net, and since I now have some socket experience, I am leaning towards 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.
I think performance, reliability and simplicity are most important, and scalability not so much an issue.
Any suggestions, experiences, resources would be appreciated!!
Tracy
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
| Web site design development | Software design and development | Macromedia flex |
| Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
