(picking up a thread from a few days ago about retrieving client headers
...)
Jerome Louvel wrote:
...
That's exactly the plan, allow the creation of a custom Call (subclass if
necessary) from the ConnectorCall or the other way around for client
connectors.
So now I've hit the 'other way
Chris,
It *is* valuable information, and I don't think we can
anticipate every
situation where people will need it. Creating a
protocol-generic API is
useful, but IMO you still need to give people access to
what's going on
behind the scenes. Even if it's a little messy :-)
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
3 matches
Mail list logo
