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 also use Call.forward() for internal dispatching only. Note that
this logic is being moved to Call.context in beta 18.
...but if it's internal this makes more sense. Great.
One question about b18. In the changes you have:
- Removed "requestHeader" and "responseHeader" variables from CallModel.
While I see they're now accessed from the ConnectorCall interface, they
don't seem to be accessible from the Call class or any of its
properties. How can a Restlet (like a filter) get access to the data?
Thanks,
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.
