-
1. Re: Client-side interceptors?
clebert.suconic Oct 19, 2009 12:18 PM (in response to jmesnil)I also thought interceptors were server side. I thought this had been changed, so that's why I used that example this way.
-
2. Re: Client-side interceptors?
timfox Oct 20, 2009 9:47 AM (in response to jmesnil)Why are you so against having client side interceptors?
-
3. Re: Client-side interceptors?
clebert.suconic Oct 20, 2009 10:02 AM (in response to jmesnil)Just ignore that JIRA for now.
I'm setting the interceptor on the client when it should be set on the server.
I confused the usage. I will close the issue as not an issue.
My bad! -
4. Re: Client-side interceptors?
jmesnil Oct 20, 2009 10:11 AM (in response to jmesnil)"timfox" wrote:
Why are you so against having client side interceptors?
I am not against them. If we decide we support client-side interceptors, I just want to make sure their use on the client-side is documented too... -
5. Re: Client-side interceptors?
clebert.suconic Oct 22, 2009 10:22 AM (in response to jmesnil)Just one thought...
Shouldn't the interceptor on the client do the intercept before sending?
While I was trying to think as an user, I thought the common use case is to avoid Message sending. On the server, you could intercept the call and avoid it... on the client you could do the same.
On the current implement, the interceptor on the client could only avoid a message receive, but the server will think the message was delivered. That could break things.
Ok, I know the user has a chance to break stuff with interceptors anyway.. but I still think it would be more use if the interception on the client was done before sending. (That would mean.. interception is always client->server, never server->client).
That's IMHO. I just think we will eventually get this kind of question from users.