replace some interceptor for events

[Turini]

There are a few interceptors that can be easily replaced by CDI events. If events
get a higher performance, we could migrate these cases (need to be well tested)

[Turini]

I'm starting some performance tests here.

[asouza]

To make this change, you have to create objects that represent each point
point of the request flow... It would be nice see some examples.
Em 02/11/2013 14:26, "Rodrigo Turini" notifications@github.com escreveu:

I'm starting some performance tests here.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/247#issuecomment-27625385
.

[Turini]

It would be nice see some examples.

wait a second and you'll see an example :)

[Turini]

related PR #248 opened, as a simple example.

[garcia-jj]

Performance results?

[Turini]

Performance results?

I'll share it soon @garcia-jj, promise! Time is not being my friend :)

[garcia-jj]

Ok, just to feed my curiosity. If performance still good or better, we can implement this change to all interceptors like serialization, download and so on.

[Turini]

we can implement this change to all interceptors like serialization, download and so on.

Yes! We can use events for this specific cases. I'm changing all this possible interceptors, just for
tests. If it works fine with a good or better performance (and a good design too) I'll send some PRs =)

[Turini]

With these last two PRs, we have now: OutjectResult, Download, Upload (plus NullUpload), Deserializing, ParameterIncluder, Instantiate and ControllerLookup observing CDI events.
There is any other case that do you think it is worth to migrate? If there is not, we can close this issue :)

[lucascs]

I'd change all infrastructure interceptors to Observers... ControllerLookup => ParametersInstantiator => Instantiate => MethodExecutor (with the interceptor stack inside it)