error running b18 on Simple

2006-08-09 Thread Chris Winters
On grabbing b18 from svn and compiling, my sample app dies immediately on any request with: Aug 9, 2006 6:16:54 PM com.noelios.restlet.connector.AbstractHttpServer handle WARNING: Error while handling an HTTP server call: Aug 9, 2006 6:16:54 PM com.noelios.restlet.connector.AbstractHttpServer

Re: managing URIs?

2006-08-09 Thread Chris Winters
Jerome Louvel wrote: Currently, the recommended way is to use the HTTP client as explained here: http://www.restlet.org/tutorial#part02 Then you can check the call's status to see if an error was returned. That's useful if you don't know in advance if it's internal or external You could

RE: Some API related questions

2006-08-09 Thread Jerome Louvel
Hi Piyush, [..] > Now we are talking taste here but I think Java packages aren't a very > good example because some of them are there since jdk 1.0 and can't > be refactored without breaking thousands of apps ..I am pretty sure > that the Sun Java API gurus don't sleep easy at night :) Good

Re: Resources and Representations

2006-08-09 Thread Chris Winters
Jerome Louvel wrote: ... Agreed, the tutorial needs to be refocused. I'm considering writing a separate tutorial that will focus only on Restlet Applications, Resources and Representations, going through a more real life example. If Chris Winters wants to contribute his BookStore application to t

Re: Resources and Representations

2006-08-09 Thread Piyush Purang
I think I will wait for those examples before I form an opinion on these matters.

Re: Some API related questions

2006-08-09 Thread Piyush Purang
Hi Jerome, > 1) Why does org.restlet.data have so many classes? Couldn't they be > divided into sub packages? See also remark 3. There is a simple reason which is that the REST style defines three and only three architectural elements: - Data Elements > org.restlet.data - Connectors> org.

RE: managing URIs?

2006-08-09 Thread Jerome Louvel
Hi Chris, Currently, the recommended way is to use the HTTP client as explained here: http://www.restlet.org/tutorial#part02 Then you can check the call's status to see if an error was returned. You could also use Call.forward() for internal dispatching only. Note that this logic is being moved

RE: Accept header vs. explicit (was: RE: representations + caching (ETags, etc.))

2006-08-09 Thread Jerome Louvel
Chris, Currently, the logic to select the best representation based on client preferences is fully reusable, see ClientData.getBestVariant() method in beta 18. However, the usage of extensions to (optionally) specify the desired media type or language or encoding is only available in the Director