I thought I should post my proposed interface for the
ExternalTransport class. I won't commit it because I can't build the
current CVS tree...
However, it uses the same script interface as ExternalParser. The
script receives a URL to retrieve and should give back a formatted
response:
Field Purpose
s Status Code
r Status Reason Phrase
m Modification Time
c Contents
t Content-Type
l Content-Length
u URL
The s/r fields are a bit difficult. Should we just require scripts to
map protocol errors to HTTP codes?
The l field is used in case the script does not retrieve the entire contents.
The u field is used in case the script receives an external redirect,
in which case it should set the s and u fields. The script shouldn't
attempt to follow the new URL because it may involve a different
protocol.
Does this seem like a reasonable interface? Should the script receive
more information? (referring URL and credentials come to mind...)
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
