[
http://jira.jboss.com/jira/browse/JBREM-604?page=comments#action_12343988 ]
Tom Elrod commented on JBREM-604:
----------------------------------
The biggest issue with doing this is that is difficult to generate the remoting data
needed on the server side, such as client session id and subsystem handler to route the
request to.
Have tried to do a best guess for this by getting the remote address for the calling
socket and take the first supported subsystem defined withint the server invoker.
Obviously all the extra remoting features such as callbacks, leasing, etc. will not be
available since thirdparty client will not be able to include the extra data needed for
this on the server side.
allow socket server invoker to accept third party requests
----------------------------------------------------------
Key: JBREM-604
URL:
http://jira.jboss.com/jira/browse/JBREM-604
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
The http server invoker (i.e. CoyoteInvoker) allows thirdparty clients to make requests
and process those requests and return raw response from handler. Really no reason that
the socket server invoker could not do this as well so that someone could write their own
socket client and send raw data to the socket server invoker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira