As a follow-up for our discussion with John, I'd like to ask for a public opinion on changing the semantics of the 'set' action (see the discussion below).
The problem is that currently 'set MYCONTEXT 10' will set the lifetime of the MYCONTEXT context to 10 seconds *and* it's action-on-expiration to the empty list (since the action list has not been given). That's the semantics of 'set' since the early days of SEC ;) This approach, however, has the following drawback -- one has to rewrite the full action list for each 'set', even if only the lifetime changes (it would be more handy to omit the action list in that cases). If one wants to erase action list altogether, 'none' could be specified for it (although it is not as effecient as having no action list at all). The only problem with going the shorter approach is the fact that the semantics of existing 'set' actions would change -- unlike before, 'set MYCONTEXT 10' would no longer discard previously defined action-on-expiration. The question is -- how many of you would support such a change? kind regards, risto On 09/22/2009 06:15 PM, Risto Vaarandi wrote: >> >> 10 May 15 04:25:12 crocus anftpd[340] logout >> set timeout on session_340_anftpd to 1 second >> reset termination action to: report session_340_anftpd notify.sh >> (because the action "set session_340_anftpd 1" wipes out any >> existing termination action, I think this is a bug) >> unalias session_340_anftpd >> ... >> >> Also I think the set command should not change any termination >> action. If the user want to use set to change both the time and the >> termination action they can explicitly use "none" as the termination >> action. >> > > My answer is somewhat late -- my apologies :( > The current behavior of the 'set' action is not a bug, but a feature > that has always been there. To explain this a bit, specifying the 'none' > action and no action list are not exactly the same -- in the first case, > some overhead is involved for invoking the action list. I ackowledge, > though, that the current need to re-specify the same action list for > 'set' is not handy. The problem is that introducing this feature to the > code will change the semantics of older rulesets. > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
