Community
Participate
Working Groups
To more cleanly separate the concerns in the file system services (and provide other channel implementations for communication such as intra-thread pipes via java.nio) o Remove all socket channel dependencies from file server commands o Add dependency on channel communicator interfaces instead o File server command factory creates communicators for client and server o Client to server initial conversation removed from abstract file server command o File server command factory handles intial conversation from client to server o File server command factory socket factory holds communicator factory instead o The underlying communication mechanism is abstracted (sockets, pipes, etc) to a java channel abstraction (sockets, files, intra-thread, all supported) o IAC could use this without socket overhead (intra-thread pipes instead) o Probably 2 to 3 days of work
Potentially target to TPTP 4.1 i3 if IAC requires this optimization (it works currently without this optimization and is quite fast without it). The main concern in my view is not optimization it is more an extensibility and design improvement.
It is important to get this in, in order to have a socketless implementation of file transfer that is conformant to the current file transfer functionality. One codebase for all cases (unsecure, secure, IAC, RAC, etc). I am raising the priority, not enough resources to implement this in i2 so I am putting for i3 (or perhaps if we can get permission to fix in first week of i2 test). Need to discuss this in Monday test project meeting since without this, test features will not function on IAC (esp. test recorder that relies on relative path functionality in 4.1).
Need to also test the starting up and shutting down of a local IAC initiated file server since the IAC will be brought up and started potentially multiple times in a single user session (cleaning up resouces as needed).
It appears that this is not an issue for the short-term due to the environment of the launched process inheriting values from the ancestor processes (and it turns out in the IAC case that the ancestral stream includes the workbench JARs (so we don't ever need to deploy anything extra to the classpath in the IAC local case). The main reason for this defect was to handle the deployment of the recorder JARs in the local IAC case -- they are not *deployed* due to the file system services having some features that the local file manager did not include (changing relative paths into absolute paths on putFile commands) but it still works since the process has the correct classpath set from the workbench.
This blocks bugzilla 126038 which was opened for a downstream product. It is needed in 4.2 (the sooner the better).
Mass update of P1 enhancements and defects targetted to future to P2.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
