No idea why I switched back to activators. Ugh.
I know why I switched back to activation: because there's a lot of plumbing involved in getting a Remote reference
Holy s*** it runs
Using binding to export activator
Local node no longer exports itself? that means peers can't getRemoteNode().getScheduler? lame.
Changing ActivatorRequestHandler to NodeProxyRequestHandler so clients can get a reference to a node instead of to its activator. Clients don't care about activation!
Local node exports self via activator and RMIRequestHandler
RMIRequestHandler provides RemoteNode instead of Activators. Eliminated concept of remote activation
Need to clarify task history stuff; defining ownership and node roles etc
Cleaning up job/task definitions
Job and Task sufficiently defined; clean up history
Cleaned up task and job removing silly properties stuff
Cleaned up task history
Checkpoint; need to rework scheduler flow.
Differentiating between local and remote scheduler interfaces
Moving RemoteNode reference ownership to LocalNode so it can provide reference to itself for scheduler
Scheduler reorganization, moving queues into their worker classes
Added Touch back to history to allow isAtInitialNode; cleaning up forwarding queue
ForwardingTaskQueue at least compiles
nixing dependence on task history