TPTP feature: 196435

Author:	Igor Alelekov
email:	igor.alelekov@intel.com
Last updated:	10/18/2007 18:04 +0400

Rough workload estimate in person weeks:

Process	Sizing	Names of people doing the work
Design	1
Code	1
Test	0.5
Documentation	0
Build and infrastructure	0
Code review & other committer work (e.g. check-in, contribution tracking) if this is to be contributed by someone who is not a committer in the component	0	N/A - will be done by committer
Total	2.5

Requirement summary

This feature should cover the work required to implement native Hyades file server in the AC. Currently, file server used in the Client Compatibility Layer (required by old Hyades clients) is implemented in Java and is accessed via JNI calls. JVM embedded in the AC is used to run this file server and Hyades security when it is enabled. Native implementation of the file server would allow JVM lazy loading - embedded JVM could be eliminated if security is not required. This would significantly reduce memory size allocated by the AC.

User interactions

Code interfaces

Should not change API.

Design summary

The AC CCTL (client compatability transport layer) has two file servers: secure and insecure. Since Hyades security implementation remains in Java, we don't need to change current Hyades secure file server implementation (we will not get a benefit in this way). Insecure file server is a Java module, logically not connected with AC. Implementation of this feature implies porting of its Java code to native code.

This should include the following:

opening server socket and listen to connecting clients
processing protocol messages in the line
performing client requests: GET_FILE, PUT_FILE, DELETE_FILE and so on
performing call back to Hyades clients since it is required by the protocol

This feature has been implemented and tested with hyades.execution file transfer tests. Implementation is available as the patch in bugzilla.