I'm looking at the streaming functionality of remoting and would like to initiate a discussion on its shortcomings and how to address.
First, it looks like the client side creates its own server connector. I don't see a way to customize it other than setting System properties for the transport, host and port. I'm thinking specifically of SSL config - I can have a very specific configuration that my client uses to talk to the server - where my truststore is, my keystore, etc. etc. - as it stands, the streaming server is just created via new Connector() - I don't see a way for me to customize that connector with my own config nor do I see a way to configure the "client" of that streaming server (which is the server that is getting data streamed to it). In other words, I would have SSL set up just the way I want between client->server, but any data I stream down the server via the streaming feature cannot be equally configured with custom SSL settings - a possible security hole. Second, it would be nice to not have to rely on System properties to define the transport/host/port config for this internal streaming server. And lastly, is there anyway to have remoting NOT create this streaming server? Since there is already a socket open to the server (my client is talking to the server over the server's normal locator URI), can we get the streamed data to be sent down over that same channel? It seems like we have a pipe there already - we should be able to use it rather than creating a separate server. Creating this separate server created problems such as the need to now configure that server (I don't want to rely on the default transport, host and port) and it will be hard to work with in an environment with firewalls and such. With those things in mind, are there any other ways to stream data from client to server without relying on this remoting streaming feature? Whether its built in to remoting or something I would have to build - doesn't matter. I just would like to know what ideas there are that would allow me to address the above issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952097#3952097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952097 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
