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 to Call.context in beta 18. Best regards, Jerome > -----Message d'origine----- > De : Winters, Chris [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 9 août 2006 06:08 > À : [email protected] > Objet : managing URIs? > > The answer is probably "however your application wants to", > but just in > case: > > If I have a representation coming back to me for a POST or PUT: > > <book> > <title>Higher-Order Perl</title> > <publishedOn>2005-02-14</publishedOn> > <author link="/author/1234" /> > <publisher link="/publisher/4321" /> > </book> > > What's the best way of verifying that the 'author' and > 'publisher' links > refer to existing resources? (Assumption is that they're all > on my site, > but I think the conclusion should hold if they're > fully-qualified URIs.) > Should I dispatch the links through my Restlet container and > see if they > come back with a 200 or a 404 status? > > Chris > > -- > Chris Winters ([EMAIL PROTECTED]) > Lead Software Developer > Vocollect Healthcare Systems > > CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and > intended for the addressee(s) only. It may contain privileged and/or > confidential information. If you have received it in error > you are not > authorized to disseminate it in any manner; please delete it and any > copies and reply to the sender that it was misdirected. > >
