>> Great stuff - I think there's a lot of cool things WW can do to become an
>> uber-command framework.
>
> Yup, but what? What is missing?
It would be cool to have a simple ActionExecutor? Something like:
ActionExecutor.execute("actionName", paramsMap);
Then of course you could have asynchronous commands:
ActionExecutor.executeAsync("actionName", paramsMap);
And queued commands (where commands are put onto a named queue, or the
default queue and executed when there is a free thread). This is very useful
for things like indexing which you don't really care if they are done
instantly - so asynchronous execution - but you also only want one command
executing at once.
ActionExecutor.queueCommand("actionName", paramsMap); // default queue
ActionExecutor.queueCommand("actionName", paramsMap, "queueName");
How about timed commands which execute repeatedly, or after a particular
delay, or at a particular time? (like a TimerTask, but bundled with a
command)
And you could have various 'batch command execution' utilities, like the
ActionPool (for parallel command execution) or perhaps an ActionList (where
commands are added, and then executed in a single go).
I'm sure there are many more ideas here - these are just off the top of my
head :)
(Warning: these make webwork far more powerful than it currently is, but
make it much more 'confusing' also?)
>> For example someone (Noah?) sent me via email his ActionPool implementation,
>> which is a funky idea!
> <snip>
>
> That is a really powerful thing, which will be great for many things
> (delegated searches come to mind). Add it :-)
Will do when I get time.
Cheers,
Mike
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Webwork-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webwork-user
