Hi Paul, We made the choice to keep the URI reference unchanged and to provide Reference.decode()/encode() static methods instead.
Now, maybe we could add getDecodedPath() and similar methods, but it might crop the class. Any thought? Best regards, Jerome > -----Message d'origine----- > De : Paul J. Lucas [mailto:[EMAIL PROTECTED] > Envoyé : lundi 10 mars 2008 17:45 > À : [email protected] > Objet : Re: Root URIs under Windows > > On Mar 10, 2008, at 1:45 AM, Thierry Boileau wrote: > > > I've tested this code below with both Restlet 1.1 (snapshot) and > > Restlet 1.0.8 and it works. > > Could you tell us more about your code? > > I have my own classes derived from Directory and > DirectoryResource. I > override DirectoryResource.handleGet(). In handleGet(), I need to > know what the Directory's "root directory" is so I call > Directory.getRootRef().getPath(). The path it returns is > URL-encoded, > e.g., spaces are encoded as %20. This is why my code fails (because > it needs to be decoded first). > > So the question is: should Reference.getPath() (and other get*() > methods) return their component strings already decoded? This would > parallel URI.getPath(). If you really want the original > form, there's > URI.getRawPath() and there could correspondingly be > Reference.getRaw*() methods. > > - Paul
