sandstorm framework plans

Hi,

I would like your feedback on seda/sandstorm plans for future.

Is there provision to make SandStorm more container-like managed? I hate big overkill containers.
But any service designer would like minimal capacities, like the following:

1-
A standard SLCE (service life cycle environment): I mean restart and gracefull shutdown, with
hooks, or at least a ShutdownSignalIf, of course allowing stage to know it, but mainly give a way
to passivate/reactivate the queues intead of killing the whole thing!

2-
to bootstrap non-eventhandlers classes. Basically only require simple object creation and
jndi-like binding.

3-
detach the whole sandstorm content in a "pluggable" classloader. (custom classloader can take care
of "jar/classes changed on disks", initiate shutdown sequence and reload service, eventually
fallback on simple java.net.URLClassLoader)

4-
(now I'll push a bit far I know) Built-in remote sinks... (but this can be worked around as any
async i/o). Only it would be a great sandstorm extension: seda.sandstorm.remote...


- - -

Sure, one could work some of these features around by a fake stage that boots a lot of stuff, and
add signals/fire shutdown signals, and stages trying to persist/refill their sink. But sound like
a lot everytime. Besides, the classloder stuff must be a top level architectural issue.


Thanks.
Dan.


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01