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/ Trying to walk that thin line between intelligence and ignorance Wed, 08 Sep 2010 21:03:45 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Davy Brion http://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 @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 @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: Adam http://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 Brion http://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: Sergejus http://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 Brion http://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: Brad http://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

]]>