Re: Question to all about visual webapps and Restlet

John, I think it's helpful to think in terms of fundamental, base resources and composite, view resources. [...] For other cases, I think it makes more sense to have the facets more or less completely disjoint. The human useful, composite views may make a lot more sense to the user if

Re: Classpath or config?

Hello Chuck, thanks for this good point. A link to the connectors page has been made from part #2 of the tutorial. Best regards, Thierry Boileau Given the number of times I've seen this question asked (both on this list and here at my company), it seems to me that the configuring of

RE: Defining Methods

Hi Sean, I don't think that there is a consensus on this point in the REST community. Some think that we should only rely on GET/POST as the other methods are not well supported by browsers. We Restlet, you can always rely on the tunnel service to dynamically change the method of request, by

RE: Question to all about visual webapps and Restlet

Hi John, [...] I think it's helpful to think in terms of fundamental, base resources and composite, view resources. An analogy is the difference between tables and views in a relational database such as Oracle. I agree, this is a useful analogy. As you noted, in your example, it could

RE: Reference not resolving

Hi John, Thanks again for the useful feed-back. You made use rethink this issue more deeply. However, as said in chapter 5.1. Establishing a Base URI, of the Uri reference (http://www.ietf.org/rfc/rfc3986.txt), a relative part cannot be used in a context where the base reference is

RE: Question to all about visual webapps and Restlet

Hi Vincent, So you're forcing one resource to be aware of other resources just because of the way your user interface in designed. If you switch to HTML frames, you no longer need these dependencies because each frame displays only one resource (the content frame, the profile frame,

a gzip representation

I was looking for some guidance on how i would package a gzipped java serialized object. Do I need to extend ObjectRepresentation class and use content type application/gzip or is there some way I can use the ObjectRepresentation class with some form of encoding. cheers /jima

RE: a gzip representation

Hi Jim, You can have a look at the com.noelios.restlet.application.EncodeRepresentation class. We are also planning on adding an automatic/configurable encoding service: http://restlet.tigris.org/issues/show_bug.cgi?id=208 Best regards, Jerome -Message d'origine- De : Jim

Re: a gzip representation

Jerome Louvel wrote: Hi Jim, You can have a look at the com.noelios.restlet.application.EncodeRepresentation class. So i can use it to wrap an ObjectRepresentation. Will the Encoding i pass across to it override the HTTP content-type header (i.e. if the encoding is set to gzip then the

Re: a gzip representation

Hi Jim, I want to precise that the EncodeRepresentation automatically sets the content-encoding header and keep intact the content-type of the wrapped representation. It allows Firefox to decodes on the fly the gzip stream and restore the wrapped representation. If you want to use

Re: Defining Methods

Hi Jerome, Jerome Louvel contact at noelios.com writes: Hi Sean, I don't think that there is a consensus on this point in the REST community. Some think that we should only rely on GET/POST as the other methods are not well supported by browsers. We Restlet, you can always rely on the

RE: Defining Methods

Hi Sean, I should have mentioned that this is a web service so browsers don't need to be involved. Does that change anything? No, if the HTTP client is somewhat limited regarding methods, the tunnel service can still be used. The result of a CANCEL is that an invoice is canceled in the

Re: Question to all about visual webapps and Restlet

I agree and would add that those lower-level resources (or core resources) could be modelled and exposed as either: - persistent POJOs (db4o, EJB3, etc.) - RESTful resources (via a separate Restlet application for example) In the second case, you could even think about a two-layer

Re: Reference not resolving

The change to getRemainingPart() catches all Exceptions and silently returns null. While the set of possible exceptions is small (StringIndexOutOfBounds and NullPointerException), this class may be extended or modified to include a wider set of failure cases. I request validation be performed

Request for change to Representation

Gentlemen, Currently, a Reference instance may be in any state from empty, to invalid, to relative, to absolute. In any of those states it may or may not have a baseRef. No exceptions appear until certain getter methods are called. I agree that we should be able to modify the parts of a

RE: Reference not resolving

Justin, I have refactored the implementation to not rely on this try/catch block anymore. Thanks for the suggestion. Thanks for testing this from SVN if you can. Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Justin C. van Vorst Envoyé