11:46 a.m.
RMI Streaming from server to client
-----------------------------------
Key: JBREM-776
URL: http://jira.jboss.com/jira/browse/JBREM-776
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.SP4
Reporter: Greg Caulton
The logical inverse of existing JBoss streams implementation is needed to stream files
from the server to the client.
CLIENT:
OutputStream out = ... (ByteArrayOutputStream or FileOutputStream as needed)
remotingClient = new Client(new InvokerLocator(streamLocatorURL));
remotingClient.connect();
remotingClient.invoke(fileOutput, parameter);
SERVER:
public Object handleStream(OutputStream stream, InvocationRequest request) {
... get file based on request.getParameter();
... standard write a file to the stream
}
On the server the bean would use the parameter to determine the file requested. For
example the parameter might be a primary key value to file meta data, or it could be a
known filepath, or bytes read from a database. Security can be handled at the application
level by the bean.
--
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
8 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-776) RMI Streaming from server to client
[ http://jira.jboss.com/jira/browse/JBREM-776?page=all ]
Greg Caulton updated JBREM-776:
-------------------------------
Description:
The logical inverse of existing JBoss streams implementation is needed to stream files
from the server to the client.
CLIENT:
OutputStream out = ... (ByteArrayOutputStream or FileOutputStream as needed)
remotingClient = new Client(new InvokerLocator(streamLocatorURL));
remotingClient.connect();
remotingClient.invoke(out, parameter);
SERVER:
public Object handleStream(OutputStream stream, InvocationRequest request) {
... get file based on request.getParameter();
... standard write a file to the stream
}
On the server the bean would use the parameter to determine the file requested. For
example the parameter might be a primary key value to file meta data, or it could be a
known filepath, or bytes read from a database. Security can be handled at the application
level by the bean.
was:
The logical inverse of existing JBoss streams implementation is needed to stream files
from the server to the client.
CLIENT:
OutputStream out = ... (ByteArrayOutputStream or FileOutputStream as needed)
remotingClient = new Client(new InvokerLocator(streamLocatorURL));
remotingClient.connect();
remotingClient.invoke(fileOutput, parameter);
SERVER:
public Object handleStream(OutputStream stream, InvocationRequest request) {
... get file based on request.getParameter();
... standard write a file to the stream
}
On the server the bean would use the parameter to determine the file requested. For
example the parameter might be a primary key value to file meta data, or it could be a
known filepath, or bytes read from a database. Security can be handled at the application
level by the bean.
RMI Streaming from server to client
-----------------------------------
Key: JBREM-776
URL: http://jira.jboss.com/jira/browse/JBREM-776
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.SP4
Reporter: Greg Caulton
The logical inverse of existing JBoss streams implementation is needed to stream files
from the server to the client.
CLIENT:
OutputStream out = ... (ByteArrayOutputStream or FileOutputStream as needed)
remotingClient = new Client(new InvokerLocator(streamLocatorURL));
remotingClient.connect();
remotingClient.invoke(out, parameter);
SERVER:
public Object handleStream(OutputStream stream, InvocationRequest request) {
... get file based on request.getParameter();
... standard write a file to the stream
}
On the server the bean would use the parameter to determine the file requested. For
example the parameter might be a primary key value to file meta data, or it could be a
known filepath, or bytes read from a database. Security can be handled at the application
level by the bean.
--
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
3:01 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-776) RMI Streaming from server to client
[ http://jira.jboss.com/jira/browse/JBREM-776?page=all ]
Ron Sigal closed JBREM-776.
---------------------------
Duplicates JBREM-661 "Allow server sending a stream to the client".
RMI Streaming from server to client
-----------------------------------
Key: JBREM-776
URL: http://jira.jboss.com/jira/browse/JBREM-776
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.SP4
Reporter: Greg Caulton
The logical inverse of existing JBoss streams implementation is needed to stream files
from the server to the client.
CLIENT:
OutputStream out = ... (ByteArrayOutputStream or FileOutputStream as needed)
remotingClient = new Client(new InvokerLocator(streamLocatorURL));
remotingClient.connect();
remotingClient.invoke(out, parameter);
SERVER:
public Object handleStream(OutputStream stream, InvocationRequest request) {
... get file based on request.getParameter();
... standard write a file to the stream
}
On the server the bean would use the parameter to determine the file requested. For
example the parameter might be a primary key value to file meta data, or it could be a
known filepath, or bytes read from a database. Security can be handled at the application
level by the bean.
--
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
3:01 p.m.
New subject: [JBoss JIRA] Resolved: (JBREM-776) RMI Streaming from server to client
[ http://jira.jboss.com/jira/browse/JBREM-776?page=all ]
Ron Sigal resolved JBREM-776.
-----------------------------
Resolution: Duplicate Issue
RMI Streaming from server to client
-----------------------------------
Key: JBREM-776
URL: http://jira.jboss.com/jira/browse/JBREM-776
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.SP4
Reporter: Greg Caulton
The logical inverse of existing JBoss streams implementation is needed to stream files
from the server to the client.
CLIENT:
OutputStream out = ... (ByteArrayOutputStream or FileOutputStream as needed)
remotingClient = new Client(new InvokerLocator(streamLocatorURL));
remotingClient.connect();
remotingClient.invoke(out, parameter);
SERVER:
public Object handleStream(OutputStream stream, InvocationRequest request) {
... get file based on request.getParameter();
... standard write a file to the stream
}
On the server the bean would use the parameter to determine the file requested. For
example the parameter might be a primary key value to file meta data, or it could be a
known filepath, or bytes read from a database. Security can be handled at the application
level by the bean.
--
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
6909
days inactive
6972
days old
3 comments
2 participants
participants (2)
-
Greg Caulton (JIRA) -
Ron Sigal (JIRA)