How do I define a root URL for my Restlet application

Hi all, I've been going through the First Resource tutorial for Restlet 1.1, and would like to find out how to define a root URL for the various routes (to resources) defined in my Restlet application. I am deploying the Restlet application as a stand-alone Java application and not in a

Redirecting via client dispatcher

Hi!, Can anyone help me explain this redirector behavior. I was testing a load balancing restlet web service basically it just redirect a request to the destination. Example http://localhost:8183/webservice/resource1/test this will be redirected to any of the specified route

RE: How do I define a root URL for my Restlet application

Hello, when you attach your application at your component, you can specify a root URL: component.getDefaultHost().attach(/firstResource, new FirstResourceApplication()); Inside your application, if you want to define a root URL for a set of branches: just attach a router: Router root = new

Subscribe

-- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2591900

RE: Redirecting via client dispatcher

Hello Gerald, -- but it is not showing or it like requesting indefinitely, no output is receive, until I stop the browser. Could you tell us what client (internal, net or httpclient, etc) and server connectors (internal, jetty, simple, grizzly, netty, etc) are you using on both servers

Re: What to do about sessions?

It's hard for me to see Comet as RESTful. I would consider it a new use of HTTP that demands a new way of thinking. You'd probably want to use a lower level API than Restlet, so you can fully leverage asynchronicity. Have you considered repeat rapid polling instead of using Comet? On

HTTPS and HTTP?

Hi, i'd like to know if there's a way to have on the same application running HTTPS resources and HTTP. My idea is to have a login resource via HTTPS where a session is returned if user/password are ok and then check the session in other HTTP resources (so the overload of HTTPS is saved) Thanks!

Re: HTTPS and HTTP?

A common solution I use is to have my loadbalancer (I like PerlBal) handles HTTPS divert HTTP and HTTPS to different ports, for example 80 for HTTP and 81 for HTTPS. You can run your Restlet component with two servers to answer both of these, and then test for which port requests are coming

Re: Protobuf, protocolbuffer

A while back I wrote a Restlet Representation that could be used for wrapping a protobuf. The code is in the issue tracker, but i never got around to cleaning it up such that it could be checked in. Unfortunately my current job makes contributing to Restlet (or any open source project) a bit

Re: What to do about sessions?

Well, I wrote my own NIO application server, so yes on both accounts! Polling is not an option, I need to support thousands of concurrent clients per hardware. http://rupy.googlecode.com /m On Thu, 22 Apr 2010, Tal Liron wrote: It's hard for me to see Comet as RESTful. I would consider it a

Re: HTTPS and HTTP?

Thanks Tal! I solved it your way i think. But without load balancer. I added HTTP server on port 80 and HTTPS on port 81 and the login resource checks the protocol like this: if(request.getProtocol() != Protocol.HTTPS) Hope that's right and make my app secure. Thank you again! -- View this