Are there provisions in HTTP to support fees for documents? I'm
looking for a mechanism that works something like this:
1) Client requests document.
2) Server rejects, requesting payment. Server informs client of cost.
Server expects some kind of (say) certificate that proves the client
has deposited money in the server's "bank account" somewhere or that
represents some kind of "digital cash". (I'm using the term VERY
loosely.)
3) If user hasn't done so already (and perhaps even if s/he has),
client requests payment authorization from user (in some unspecified
form).
4) With payment in hand, client re-requests document from server.
Thanks for any pointers.
Dave Kristol