On 10/25/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Is this parameter read from the file every time, or is it taken from the memory after the first loading. If latter is the case, don't think it will have an considerable affect on performance.
Thanx,
Chamikara
----- Original Message -----From: Chamikara JayalathSent: Tuesday, October 25, 2005 5:10 PMSubject: Re: Need for a global Duplicate Detection HaldlerHi Deepal,
You mean a Global DuplucateDetection module ??
Duplicate detection is a part of RM logic. So making it a module does not seem right to me. (for security case it may be ok, since they may be dividing it as encryption, authontication ect. which are different functionalities users need).
And users having to attach two modules also does not sound very nice. A single RM module (global or service specific) sound much better.>>>>>>>>>>>>agreed>>>>>>>>>>>>>
Can we go for something like this. We make Sandesha a global module. We add an RMPhase (after PostDispatch) and make sure that the service specific handlers are attached to that phase. And we attach the DuplicateDetection handler to the PreDispatch phase (which is global). Within the RM Service specific handlers we check weather a special parameter is made "true" in the service.xml. RM will only happend if that parameter is "true" for the service. So RM will happen only for RM enabled services.>>>>>>>>>>I always like to make the simple case simple , if you try to put some parameter in service.xml and at each invocation you are going to check that parameter , it will make system slow down. So my personal view is we should not do that , if we have some other option it will be great>>>>>>>>>
Is this parameter read from the file every time, or is it taken from the memory after the first loading. If latter is the case, don't think it will have an considerable affect on performance.
Thanx,
Chamikara
