Tijs
- make it possible to have more than one Synapse configuration flow
instantiated when starting a Synapse server
What I mean with this is that as for as I know, one Synapse configuration flow
is given as parameter when starting the Synapse serverr. By default Synapse
searches for a synapse.xml file in the repository conf directory. If this is
true, I think it would be a nice improvement to support multiple configuration
flows in stead of only one.
I am planning to support starting up of a Synapse node pointing at a
registry URL. This means that you may be able to define and/or store
more than one synapse configuration in the registry (say as
http://registry/config1 and http://registry/config2.. etc) and the node
is directed to fetch its complete configuration from the registry. This
also means that as any other resource loaded from the registry, the
configuration itself could be dynamic if required. This way, you could
even define http://registry/staging and http://registry/production
configurations into the registry and start off a few nodes with the
same/different configurations as required. Is this same as what you expect?
Quartz scheduling would be nice to support functionality to do bulk invocations
to a service. So Synapse stores incoming messages and a specified time
intervals a service is called with all the messages that have been sent to
Synapse.
Hmm.. I guess this would be nice to have... but the FTP/File support
Paul brought up a few days earlier also comes to my mind as useful. But
I agree with Paul that we could focus on features such as these post 1.0
after we nail down NIO and performance and the other basics.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
