Hugh Nelson wrote:
If you use http as a transport, how do you provide a store and forward mechanism? Would that involve Argusconnect providing a central location like hotmail?
Good question. As Richard Hosking rightly describes in another posting, HTTP does not need any sore-and-forward mechanism. However he omits to describe those business/political models that necessitate some form of store-and-forward. Prescription processing as one example needs some mechanism to allow prescriptions remain on a 'holding server' until picked up by a pharmacy to whom the patients has gone to. ie a situation where the sender doesnt know who the recipient is going to be, and a recipient who doesnt know who the sender will be until he is notified by the patient. However there are other examples of situations where a store-and-forward mechanism may be desirable. In the Web services world, there are a few ways to implement this but the most common solution is to have an 'intermediary' just for those type of transactions and then a direct notification to the recipient to go to that intermediary to pick up the message. Now who provides that intermediary is probably the 'ten million dollar question' and is playing on the minds of many in the healthcare industry. cheers Ross ------------------------------- Ross Davey CEO ArgusConnect Pty Ltd _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
