Ticket #83 (accepted enhancement)

Opened 6 years ago

Last modified 2 years ago

Upgrade Remote Executor classes

Reported by: Joel Owned by: Joel
Priority: major Milestone: Eraser 6.1/6.2
Component: Core Version:
Keywords: Cc:
Processor Architecture: Blocked By:
Blocking: #278, #299, #355, #362 Operating System:

Description

The current Remote Executor classes only allow task addition and deletion, but the other functionality like events and other functions are not implemented like the DirectExecutor? class. The ideal implementation will allow clients to use the RemoteExecutorClient? class like it was doing DirectExecutor? now.

Change History

comment:1 Changed 5 years ago by Joel

  • Blocking 278 added

comment:2 Changed 5 years ago by Joel

  • Blocking 239 added

comment:3 Changed 5 years ago by Joel

  • Blocking 239 removed

comment:4 Changed 4 years ago by Joel

  • Blocking 355 added

(In #355) This ticket needs to have a good interface for RPC -- the "wait" function needs this so that it will return only when complete.

comment:5 Changed 3 years ago by Joel

  • Blocking 362 added

(In #362) The Remote Executor classes should use the XML format for better interoperability with other non .NET clients (e.g. unmanaged code)

comment:6 Changed 3 years ago by Joel

  • Status changed from new to accepted
  • Owner set to Joel

Work started in r2623.

comment:7 Changed 2 years ago by Joel

As of r2759, the code is able to call and receive events from Eraser's Executor engine running in a different process. Progress made! :)

comment:8 Changed 2 years ago by Joel

  • Blocking 299 added

(In #299) On further review, this can almost already be achieved with r2737 without needing a service.

Note: See TracTickets for help on using tickets.