Comments on: One-Way (Or Fire And Forget) Requests With Agatha http://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/ inquisitive: adjective. given to inquiry, research, or asking questions; eager for knowledge; intellectually curious Wed, 08 Feb 2012 11:42:42 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Davy Brionhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-98763 Davy Brion Thu, 24 Mar 2011 12:08:00 +0000 http://davybrion.com/blog/?p=1989#comment-98763 if you want to add multiple requests of the same type, you need to add them with a key (there's an overload for it) so they can be identified. When the results come back, you can retrieve them with the key with which they were added if you want to add multiple requests of the same type, you need to add them with a key (there’s an overload for it) so they can be identified. When the results come back, you can retrieve them with the key with which they were added

]]> By: Darryl Waterhousehttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-98762 Darryl Waterhouse Thu, 24 Mar 2011 11:16:00 +0000 http://davybrion.com/blog/?p=1989#comment-98762 This is a quite generic question. We already use Agatha for handling the bundling of our Service calls. If I send an XML bundle with three requests, the first and the third being of an identical type; Will Agatha guarantee that the response will be in the same order as the requests were supplied? A difficult question, but I'm guessing that Davy, or one of you guys will know this already!Thanks in advance! This is a quite generic question.
We already use Agatha for handling the bundling of our Service calls.
If I send an XML bundle with three requests, the first and the third being of an identical type; Will Agatha guarantee that the response will be in the same order as the requests were supplied?
A difficult question, but I’m guessing that Davy, or one of you guys will know this already!

Thanks in advance!

]]> By: Michael Wolfendenhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-98289 Michael Wolfenden Thu, 03 Mar 2011 02:03:00 +0000 http://davybrion.com/blog/?p=1989#comment-98289 In my application I have both normal requests (think queries) and one way requests (think commands).I created a custom unit of work dispatcher which opened a unit on work in BeforeSendingRequests and then in BeforeReturningResponses either rolledbacked or commited depending on whether an errors occured.This doesn't work for One Way Requests as BeforeReturningResponses is never called (which makes sense). I thought about using AfterSendingRequests but I have no responses to check for errors when called with non-one way request.How can I handle this situation ?Thanks In my application I have both normal requests (think queries) and one way requests (think commands).

I created a custom unit of work dispatcher which opened a unit on work in BeforeSendingRequests and then in BeforeReturningResponses either rolledbacked or commited depending on whether an errors occured.

This doesn’t work for One Way Requests as BeforeReturningResponses is never called (which makes sense). I thought about using AfterSendingRequests but I have no responses to check for errors when called with non-one way request.

How can I handle this situation ?

Thanks

]]> By: Davy Brionhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-23205 Davy Brion Mon, 14 Dec 2009 10:13:57 +0000 http://davybrion.com/blog/?p=1989#comment-23205 @Adamif there is a problem with handling the request, it will be logged by Agatha in the server-side logif there is a problem with sending a synchronous one-way request, you will get an exception (since it blocks until the request is _sent_ but once it's sent, the call returns)if there is a problem with sending an asynchronous one-way request, then you'll indeed never know about it @Adam

if there is a problem with handling the request, it will be logged by Agatha in the server-side log

if there is a problem with sending a synchronous one-way request, you will get an exception (since it blocks until the request is _sent_ but once it’s sent, the call returns)

if there is a problem with sending an asynchronous one-way request, then you’ll indeed never know about it

]]> By: Adamhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-23204 Adam Mon, 14 Dec 2009 10:08:03 +0000 http://davybrion.com/blog/?p=1989#comment-23204 What happens if there are problems with sending or handling the request? I suppose the client will not notice at all, in which case it should only be used for requests that can be lost. This has to be carefully evaluated to avoid breaking the application. What happens if there are problems with sending or handling the request?
I suppose the client will not notice at all, in which case it should only be used for requests that can be lost. This has to be carefully evaluated to avoid breaking the application.

]]> By: Davy Brionhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-23184 Davy Brion Sat, 12 Dec 2009 12:33:35 +0000 http://davybrion.com/blog/?p=1989#comment-23184 it's not possible yet, but i think it could be done. We'd need a MSMQ-specific implementation of IAsyncRequestProcessor which adds the one-way requests to the queue and you'd need a server-side component which reads the messages (the one-way requests) off of the queue and pushes them to the Request Processor. it’s not possible yet, but i think it could be done. We’d need a MSMQ-specific implementation of IAsyncRequestProcessor which adds the one-way requests to the queue and you’d need a server-side component which reads the messages (the one-way requests) off of the queue and pushes them to the Request Processor.

]]> By: Sergejushttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-23175 Sergejus Fri, 11 Dec 2009 18:00:47 +0000 http://davybrion.com/blog/?p=1989#comment-23175 I really like Agata as is, but is it possible to use it with MSMQ (async model for Send and sync model for Receive)? I really like Agata as is, but is it possible to use it with MSMQ (async model for Send and sync model for Receive)?

]]> By: Davy Brionhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-23089 Davy Brion Sat, 05 Dec 2009 10:17:01 +0000 http://davybrion.com/blog/?p=1989#comment-23089 Agatha doesn't require WCF, though you would have to configure it slightly differently than usual and the OneWayRequest stuff wouldn't truly be one-way either (unless you use the async proxy)Other than that, it should work just fine... i suggest you just give it a shot in a spike and see for yourself whether you like it or not Agatha doesn’t require WCF, though you would have to configure it slightly differently than usual and the OneWayRequest stuff wouldn’t truly be one-way either (unless you use the async proxy)

Other than that, it should work just fine… i suggest you just give it a shot in a spike and see for yourself whether you like it or not

]]> By: Bradhttp://davybrion.com/blog/2009/12/one-way-or-fire-and-forget-requests-with-agatha/comment-page-1/#comment-23088 Brad Fri, 04 Dec 2009 20:16:46 +0000 http://davybrion.com/blog/?p=1989#comment-23088 Hi, I am working on an ASP.NET MVC project and I'm very interested in using a Request/Response architecture to help simplify the project. We don't need WCF/Silverlight (not yet, at least). Furthermore, to facilitate database transaction rollbacks and more generally just to keep things simple, we would like to maintain synchronized program flow. Is Agatha overkill for our needs? Does Agatha require WCF to operate correctly? Any suggestions for using Agatha in an MVC project?Thanks,Brad Hi, I am working on an ASP.NET MVC project and I’m very interested in using a Request/Response architecture to help simplify the project. We don’t need WCF/Silverlight (not yet, at least). Furthermore, to facilitate database transaction rollbacks and more generally just to keep things simple, we would like to maintain synchronized program flow. Is Agatha overkill for our needs? Does Agatha require WCF to operate correctly? Any suggestions for using Agatha in an MVC project?

Thanks,

Brad

]]>