-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
High
A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered.
Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports.
1.
|
Remoting 2 "socket" protocol client emulation | Closed | Unassigned | ||
2.
|
Remoting 2 "socket" protocol server | Closed | Unassigned | ||
3.
|
Remoting 2 "sslsocket" protocol client emulation | Closed | Unassigned | ||
4.
|
Remoting 2 "sslsocket" protocol server | Closed | Unassigned | ||
5.
|
Remoting 2 "bisocket" protocl client emulation | Closed | Unassigned | ||
6.
|
Remoting 2 "bisocket" protocol server | Closed | Unassigned | ||
7.
|
Remoting 2 "sslbisocket" protocol client emulation | Closed | Unassigned | ||
8.
|
Remoting 2 "sslbisocket" protocol server | Closed | Unassigned | ||
9.
|
Implement Remoting 2 Callback emulation | Closed | Unassigned | ||
10.
|
Remoting 2 entity metadata | Closed | David Lloyd | ||
11.
|
Remoting 2 servlet http protocol server emulation | Closed | Unassigned | ||
12.
|
Remoting 2 discovery protocol emulation | Closed | Unassigned |