Hi, Let's say I have a set of REST services some of which accept (optional) paging parameters in query strings (like "page=2&page_size=20"). I want to access these parameters in service methods without resorting to adding a bunch of them directly as parameters to methods.
I could use WebOperationContext.Current to read the values from HTTP request, but I want to avoid this for obvious reasons (the ability to unit-test in isolation is one). Is there some kind of service implemented in Castle's WCF integration which I could constructor- inject into my services and use to access the request properties? If not, what would be the best way to implement this myself? I'm concerned about the lifestyles of my services: they obviously need to be transient/perWebRequest in order for this to work. Thanks in advance, Igor -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
