batching/lazy

[Ramon Smits]

Does anyone have an implementation that 'batches' requests via a lazy response implementation?

--

Ramon

[Davy Brion]

do you mean an implementation that only sends the requests once a property of a response object is accessed? the current implementation delays sending the requests until a response is retrieved through GetResponse<TResponse>

[Ramon Smits]

do you mean an implementation that only sends the requests once a property of a response object is accessed? the current implementation delays sending the requests until a response is retrieved through GetResponse<TResponse>

Yes I know, but this makes IRequestDispatcher known to the caller. If would be pretty awesome if for example there would exist something like:


Lazy<T> IRequestDispatcher.AddLazy<T>(Request request);

or maybe even lazy proxy like behavior as for example NHibernate provides.

[Davy Brion]

it would be sorta cool, but i doubt if it'll introduce a noticeable benefit :)

[Ramon Smits]

On Wed, Apr 4, 2012 at 2:18 PM, Davy Brion <ral...@davybrion.com> wrote:

it would be sorta cool, but i doubt if it'll introduce a noticeable benefit :)

Well, the benefit would be that if you have multiple controllers that all perform requests and share one IRequestDispatcher that all these actions are batches and perform a roundtrip when the first view model action takes place without letting a result processor know anything about Agatha.

[Davy Brion]

are you talking about asp.net mvc controllers? or something custom made?

in any case, request dispatchers aren't meant to be shared... they keep the WCF connection open for the duration of their lifetime, and there are no thread safety provisions either