1 Reply Latest reply on Nov 12, 2007 2:55 AM by Ron Sigal

    JBoss Remoting Clients (not using InvokerLocator)

    Vinicius Carvalho Apprentice

      Hi there! I was looking in the docs, is it possible to use jboss remoting to be listening to a client that does not uses InvokerLocator? For instance, the create a TFTP service? I've seen that I can manipulate the socket using SocketCreationListeners. But after that my processing chain continues right? I got interested on the Remoting project because it adds a lot of functionalities that I need to implement if I go for a bare TFTP server using common-net for instance.


        • 1. Re: JBoss Remoting Clients (not using InvokerLocator)
          Ron Sigal Master

          It's not impossible to connect a "non-Remoting" client to a Remoting server. See, for example, the classes RawTestClient and RawTestServer in the package org.jboss.test.remoting.transport.socket.raw. You should be aware of the following:

          1) As of version 2.0.0, Remoting expects a version byte to precede each transmission. You would have to handle that explicitly. Or, you could set the version on the server with the flag -Djboss.remoting.pre_2_0_compatible=true, in which case the server won't expect the version byte.

          2) There are facilities like connection leasing that are handled by a Remoting client that wouldn't be available, unless you implemented yourself.

          However, as demonstrated in RawTestClient, you *can* send any kind of object to the server, without wrapping it in a Remoting specific org.jboss.remoting.InvocationRequest.

          If you give it a try, let us know how it goes.