On Tue, 2004-09-21 at 16:09 +1000, Andrew Cowie wrote: > Quick survey: I'm building something that requires a lot of two-way > (message/event) traffic between clients and servers, and could use some > help picking a technology.
Well, in my consulting days, when a client asked me an open ended, unqualified question like that... I'd tell them they need to get out their cheque book. Whats a lot - 10K messages per second? per hour? per year? Whats the mean and median message size? Are you looking at instant delivery, or reliable delivery? Neither or both? Is a lossy environment acceptable, or lossless? For what value of loss? Are your clients static or mobile? What are your encryption, repudiation, authentication needs? Are there other constraints, like the use of a specific programming language on the client or the server, or a specific client or server platform? Are the clients embedded (i.e. washing machines or pdas), or full-function pc's? Or something different? Will they be @ internet cafe's, home connections? Corporate internal infrastructure? What sort of bandwidth will they have available ? Are you looking for something with a company & commercial support, or something that you can just use [and therefore repair yourself !]. Are you able to use an opensource framework, or do you need closed-source on the client, or variations on that theme? The above questions can shape the possible answers to other questions - i.e. The use of IP as a transport, or a higher protocol (i.e. smtp| jabber|ftp|http) ... > It's pretty impressive, but seems like an awful > lot of framework for what I would have hoped would have been a simple > implementation, especially considering that I view the problem in > message passing terms, not remote procedure calls or remote object > invocation terms. That said, the scalability, availability, and just- > works factor (once implemented) is alluring. Funny thing jumped out at me here... I was taught about oop in terms of message passing: there is no conceptual difference between passing a message and a 'remote object invocation'. Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
