Yeah, Matt is dead on, local state is going to be important. There are cases where you can avoid explicit messaging. Just check local state (distributed hash) if info is available. If yes -> display, not -> 404 & one way message to get that data. On startup this info can be loaded to local state using special "GetDataOnStartUp" message. So 404 is a failure case scenario when local state is empty for some reason. But local state takes resources, so you can't have everything in there, especially for custom reporting scenarios. In this case you still need to do explicit messaging. If you are going to use messaging I'd avoid RPC style services, be it SOAP or REST. I mean, why services for reading & messages for "writing"/commands, when you can easily do both through messaging?
P.S. I forgot to say it's all just my humble opinion ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
