frank
|
72d284de7d
|
Switch to Apache license
|
2012-04-03 04:54:14 -07:00 |
Kelven Yang
|
8d8775b533
|
bug 6745: Using UUID instead of integers - for Async Jobs
|
2011-11-03 07:33:58 -07:00 |
alena
|
6f55c4dd7e
|
bug 8270: Synchronize on 1) ipAddress object when create/delete ipForwarding/portForwardingRule and vpn service 2) on networkId when assignTo/removeFrom/deleteLoadBalancer
status 8270: resolved fixed
|
2011-02-03 18:45:49 -08:00 |
will
|
c67d26cec4
|
bug 6969: First step of now displaying pending async jobs for listXXXCommands. There is a lot more cleanup and fixing to do but all commands acting against VirtualMachines now work.
|
2010-11-30 19:12:09 -08:00 |
Alex Huang
|
1e44925564
|
api refactoring
|
2010-11-21 12:00:21 -08:00 |
Kris McQueen
|
3f6a438d92
|
Refactoring the AsyncJobManager to queue jobs appropriately if there is a need to synchronize execution on an object, e.g. a router. API developers can now call command.synchronizeCommand(String, Long) to force the command to be synchronized on a particular object type [the string arg] with a particular id [the long arg]. When synchronizeCommand() is invoked, an exception maybe thrown by the framework (AsyncCommandQueued exception) to force the business logic to abort. The command will then be queued and invoked at the appropriate time. The synchronizeCommand() is re-entrant and will be a no-op if the command has already been queued and is now ready for execution.
|
2010-09-16 19:05:06 -07:00 |
Manuel Amador (Rudd-O)
|
05c020e1f6
|
Source code committed
|
2010-08-11 09:13:29 -07:00 |