Re: Server Interface Binding

2007-07-08 Thread Alex Milowski
On 7/8/07, Jerome Louvel <[EMAIL PROTECTED]> wrote: Hi Alex, You are correct, I missed this point. Thanks for looking into it and providing a patch. I was able to fix this by optionally passing in an InetAddress instance. I'm going to clean it up a bit and I'll send out a patch against the c

RE: Server Interface Binding

2007-07-08 Thread Jerome Louvel
:22 > À : discuss@restlet.tigris.org > Objet : Re: Server Interface Binding > > On 7/7/07, Jerome Louvel <[EMAIL PROTECTED]> wrote: > > > > Alex, > > > > It looks fine to me at the Restlet level... In Component, > the code looks ok: > > > >

Re: Server Interface Binding

2007-07-08 Thread Alex Milowski
On 7/7/07, Jerome Louvel <[EMAIL PROTECTED]> wrote: Alex, It looks fine to me at the Restlet level... In Component, the code looks ok: public Server add(Protocol protocol, int port) { Server result = new Server(getContext(), protocol, null, port, getTarget());

RE: Server Interface Binding

2007-07-07 Thread Jerome Louvel
reproduce the issue? Best regards, Jerome > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la > part de Alex Milowski > Envoyé : jeudi 5 juillet 2007 23:03 > À : discuss@restlet.tigris.org > Objet : Server Interface Binding > > I ha

Server Interface Binding

2007-07-05 Thread Alex Milowski
I have code (components) that use the following API call: String addr = ... int port = ... getServers().add(Protocol.HTTPS,addr,port); but I still see the process binding to the any interface "*" rather than a specific interface. I'm using the Simple framework. Is there a limitation here