Tag | MSMQ Posts

If you are designing a system that uses MSMQ over HTTP then you need to take into account that you can only push messages around the system and not pull them. So you can send from Machine A to Machine B but you can't do a similar remote receive from B to A. The reason for this is that remote receives always use the RPC protocol even if you are specifying DIRECT=HTTP or DIRECT=HTTPS. The functionality used to be present in Windows XP before service pack 2 but was withdrawn because of the limitations ...
I have a situation where I want to use a transaction to keep track of a particular message process in order to roll back various parts if there is a failure. The service operation is listening on a queue using the NetMSMQBinding and the operation is marked with the transaction properties of the OperationBehavior like so: <OperationBehavior(Trans... Public Sub SendHello( ... Using the above attribute enables the operation for transaction ...
I have been working lately with a big group of fellow developers here in SilverKey on the architecture and design of a relatively big project that required much services and messaging work. We thought that we should implement our public services the REST way using WCF for .NET 3.5, with so many customizations, and that we'll use a library called nServiceBus for internal messaging. Mohammed Nour wrote a little about thinking in REST. nServiceBus is a framework for handling publisher/subscriber (pub/sub) ...
This is the email I sent to SilverKey Tech. Egypt dev team yesterday, sharing here as usual. Article: Info Q: Don't Let Consumers and Service Providers Communicate Directly Just because someone is developing with Web Services does not mean they are following SOA principles Just because you're using HTTP and HTML doesn't mean you get into that camp and vice versa Weblog: "Making IT work" - Musings of a Holistict Architect Weblog: Udi Dahan Article: Autonomous Services and Enterprise Entity Aggregation ...