Hi Sanjiva: > +1 .. working on a kinda re-design of the config language- it needs a > ground up orthogonal design! Need a few more days and will send a > proposal.
Cool, I'll hold off on changing anything until after that. Looking forward to it! Can we discuss this on the chat tomorrow? --Glen > On Tue, 2006-04-18 at 19:39 -0400, Glen Daniels wrote: > > We should, IMO, change the configuration file for synapse to have a > > <mediation> wrapper element for the mediator configuration. > Right now > > there's no way to configure Synapse-wide properties, settings, or > > configure other things we might want to add to Synapse that aren't > > specifically mediators (see next message for an example). > > > > I'd like the resultant file to look like: > > > > <synapseConfig xmlns="synapse-ns"> > > <parameter name="foo" value="bar"/> > > > > <mediation> > > <engage-addressing-in/> > > ... > > </mediation> > > > > <otherConfig> > > ...more stuff here... > > </otherConfig> > > </synapseConfig> > > > > This would also let us get away from the <none> pattern, > which I think > > is kind of silly. :) Instead we could do something like: > > > > <synapseConfig xmlns="synapsens"> > > <mediation> > > ...mediators which always run... > > </mediation> > > > > <mediatorConfig> > > ...mediators which can only be activated by ref="" above... > > </mediatorConfig> > > </synapseConfig> > > > > Thoughts? > > > > --Glen > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
