> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > Carsten Ziegeler wrote: > > Stefano Mazzocchi wrote:
<snip/> > > For b) I'm not sure. It might make sense to execute actions after > > the xml pipeline is executed. But changing this is incompatible! > > Existing sitemaps would then be executed differently than before. > > For example, if you have > > <match> > > <generate/> > > <serialize/> > > </match> > > <act/> > > the action is currently only executed, if the match is not successful. > > Changing this would execute the action always! > > So I'm -0.5 on this. > > Agreed. -1 as well. Well, until somebody comes up with the need for an > action to be executed *after* a serializer. How about this one: if the serializer doesn't throw an exception then you *know(?)* the client recieved the request. An action after serialization maybe to log the fact that they got it perhap for usage charging...? J. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
