| Re: [swordfish-dev] Interceptor framework design options |
Ok, to put that discussion on a more concrete level, I will meet with
Jerry on Thursday or Friday to discuss examples of real life scenarios and how they would be implemented in the context of the described proposals.
In the mean time everybody is welcome to contribute examples / ideas of interceptors that are typically / important or difficult for some reason – either here in the list or on the discussion page of the proposal.
Regards
Juergen
On 11/16/09 12:06, "Andreas Mattes" <Andreas.Mattes@xxxxxxxxx> wrote:
It's a matter of fact that while from an academical point of view it is
entirely correct to demand interceptors to be context-free components,
things tend to become different when nasty practical details like the
need of performance optimization must be considered and
context-dependent information is needed e.g. in order to control caching.
Therefore, while interceptors should remain "logically" context-free,
they must be able to access their context in a well-defined way. As a
rule of thumb I would say that an interceptor should be able to work
equally (except when its task is context-related as in Jerry's example)
when the context is not accessible.
Regards,
Andreas
Gerald Preissler schrieb:
> I agree that it is not the interceptor’s business to decide whether it is to be called or not in a given context. But often the context also will drive the concrete functionality an interceptor will provide. An example: a message tracking interceptor would have to include this information in the tracking events. That’s the kind of situation that my question was aimed at.
>
> regards
> Jerry
>
>
> On 13.11.09 16:39, "Jürgen Kindler" <juergen.kindler@xxxxxxxxx> wrote:
>
> Hi Jerry,
>
> An interceptor could certainly try to figure out in which context is is being called, but in fact it is not desired.
> The interceptor should not actively need to “understand” for which context it gets activated (though implicitly it might be implemented for acting in a certain context!). It would be a matter of configuration about where a specific interceptor gets called.
>
> Cheers
> Jürgen
>
> On 11/13/09 14:48, "Gerald Preissler" <gerald.preissler@xxxxxxxxx> wrote:
>
> I take it that there will be a way for an interceptor to figure out message exchange type, role and message? In that case I’d vote for Zsolts approach.
>
> regards
> Jerry
>
>
> On 12.11.09 15:52, "Oliver Wolf" <oliver.wolf@xxxxxxxxx> wrote:
>
> Dear fellow Swordfishers,
>
> I've created a short Wiki article summarizing our design discussion on
> the Interceptor framework:
>
> http://wiki.eclipse.org/Swordfish_Documentation:_Architecture:_Interceptor_Framework
>
> Please feel free to comment on and/or add to as you see fit.
>
> Thanks,
> Oliver
>
>
> _______________________________________________
> swordfish-dev mailing list
> swordfish-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/swordfish-dev
>
>
>
--
Dr. Andreas Mattes
Software Engineer
Tel.: +49 228-182 190-33
Fax: +49 228-182 191 93
Mobil: +49 160-9631 4478
andreas.mattes@xxxxxxxxxx
SOPERA GmbH - Open Source SOA
Subscription Services, Support & Maintenance, Training,
Technical SOA Consulting & Customized Development
www.sopera.com
SOPERA GmbH · Geschäftsführer: Dr. Ricco Deutscher, Harald Weimer, Peter
Spiegel
Standort Bonn: Sträßchensweg 10 · 53113 Bonn · Handelsregister: Bonn HRB
15336
Standort München: Hohenlindnerstraße 11b · 85622 München
Vertraulichkeitshinweis: Diese Nachricht und jeder übermittelte Anhang
beinhaltet vertrauliche Informationen und ist nur für die Personen oder
das Unternehmen bestimmt, an welche sie tatsächlich gerichtet ist.
Sollten Sie nicht der Bestimmungsempfänger sein, weisen wir Sie darauf
hin, dass die Verbreitung, das (auch teilweise) Kopieren sowie der
Gebrauch der empfangenen E-Mail und der darin enthaltenen Informationen
gesetzlich verboten ist und gegebenenfalls Schadensersatzpflichten
auslösen kann. Sollten Sie diese Nachricht aufgrund eines
Übermittlungsfehlers erhalten haben, bitten wir Sie, den Sender
unverzüglich hiervon in Kenntnis zu setzen.
_______________________________________________
swordfish-dev mailing list
swordfish-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/swordfish-dev