When to Wait for Messages

Dealing with SSL Certificate Validation Failures

Nicholas Allen's Indigo Blog — Thu, 09 Nov 2006 20:22:48 GMT

Here's a quick list of things to try when debugging a non-functioning SSL server certificate. Has the

re: When to Wait for Messages

Udi Dahan -The Software Simplist — Fri, 10 Nov 2006 19:21:42 GMT

If we were to divide up different message types to different endpoints, grouping those that needed transactional behavior to the same endpoint, then we could reach a simple solution.

If the endpoint will be handling "transactional" messages, it would just open a transaction and call Receive with an infinite timeout.

Simple.

re: When to Wait for Messages

Nicholas Allen — Tue, 14 Nov 2006 10:40:50 GMT

Udi,

That's an interesting approach, assuming that you're willing to deal with having multiple endpoints. However, there are some other problems that can come up when using large timeouts. For example, if your transactional channel is layered over a channel that is willing to continuously perform work up until the timeout, such as reliable messaging. In that case, you could be spending a lot of time failing to receive the same message repeatedly. With small timeouts, the underlying channel is forced to give up after a while and move on to processing new messages.

New and Notable 126

Sam Gentile — Sat, 18 Nov 2006 17:12:56 GMT

I have lots of stuff collected up today. Software Architecture/SOA Arnon Rotem-Gal-Oz has made available

TryReceive and Exceptions

Nicholas Allen's Indigo Blog — Fri, 04 May 2007 21:21:41 GMT

After an earlier article about receiving messages , Kenny Wolf suggested that I talk about the exception

New and Notable 126

Sam Gentile — Sat, 20 Oct 2007 22:32:15 GMT

I have lots of stuff collected up today. Software Architecture/SOA Arnon Rotem-Gal-Oz has made available