Comments on: Request/Response Service Layer: Handling Requests

By: Tray Weeds

Tray Weeds — Mon, 14 Mar 2011 14:30:00 +0000

Thanks for the response Davy. If you’re planning a rewrite/refactoring, may I suggest planning for an easier way to unit test derived request processors. Maybe some sort of stub like the async processor on the client side. Testing the handlers is straightforward, but not so much for any request processors that I create. It’s been tough deciding how to mock out the config constructor argument.

I’ll also post future questions on the official forum.

By: Davy Brion

Davy Brion — Thu, 10 Mar 2011 10:49:00 +0000

There’s currently no good way of doing that (only authenticating the first request of a batch) i’m afraid. The only way to do it is to provide your own Process method, but apparently that method is not marked virtual so you can’t do that unless you provide a different IRequestProcessor implementation altogether

We always did authentication on a per-request level so we did in a custom handler base class.

Making the exception handling mechanism easily pluggable is something that i’ve been meaning to do for a long time, but it hasn’t been done yet… I do plan to start working on a new major version of agatha in april in which i hope to solve things like this.

Also, for future reference: it’s better to ask Agatha related questions on the Agatha discussions group (http://groups.google.com/group/agatha-rrsl/) so other people can answer as well, and to make answers more easily available to other people as well

By: Tray Weeds

Tray Weeds — Thu, 10 Mar 2011 03:10:00 +0000

Davy, you mention at the end of this point that I could inherit from the default RequestProcessor if I wanted to perform some authentication on the first request, but I’m having trouble figuring out which method to override on the RequestProcessor. I figured I’d start with void BeforeProcessing(IEnumerable requests), but this method doesn’t return anything and if I through a security exception out of it the client ends up seeing a HTTP 500 error instead of a nice typed exception.

How would you go about doing that?

By: Davy Brion

Davy Brion — Wed, 09 Mar 2011 14:05:00 +0000

yup: http://groups.google.com/group/agatha-rrsl/browse_thread/thread/9319d5efdbd53d6a?hl=en_US

By: Paul McNamara

Paul McNamara — Wed, 09 Mar 2011 14:01:00 +0000

Quick question, is it easy to change the service endpoint uri in code? This can be passed into my SL app as an argument so I need to be able to change it on the fly.

By: Paul McNamara

Paul McNamara — Wed, 09 Mar 2011 11:54:00 +0000

I think since I was so close anyway it might be more pain than gain to switch wholesale to your framework but it does look good. I’ll have a play this afternoon and see how far I get.

By: Davy Brion

Davy Brion — Wed, 09 Mar 2011 10:11:00 +0000

if you want to use this, don’t just take the code from these posts… it’s now an official OSS project called Agatha so you can just use that

check here for more details: http://code.google.com/p/agatha-rrsl/

By: Paul McNamara

Paul McNamara — Wed, 09 Mar 2011 10:08:00 +0000

I’m glad I found this. I was half way to doing this already (unique request and response types and even a DoMultiple method that took a collection of requests) but I still had separate service methods for each request type. This way is much cleaner and more flexible. Thanks for helping my thinking along

By: kurt schroeder

kurt schroeder — Thu, 10 Dec 2009 20:09:31 +0000

this is f’n great!