Re: HEAD not well supported?

interface in REST refer to inter-application semantics, not intra-application. And it doesn’t, to my understanding, mean that HEAD GET must have identical semantics, rather that the semantics of a GET or HEAD request be the same for all resources. Am I misunderstanding you here? best, Erik Hetzner

Re: HEAD not well supported?

that current design is appropriate. I would even go further by removing the Resource.handleHead() method and make the Finder class call handleGet() directly instead. […] Not my place, perhaps, but I am agreed. best, Erik ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D

Re: HEAD not well supported?

sense to share the logic. Also, intuitively allowHead is a bit redundant, since any resource that allows a GET really should allow a HEAD. best, Erik Hetzner pgpBRvwZrLpJV.pgp Description: PGP signature

Re: HEAD not well supported?

methods. Specifically, there are some status codes that are appropriate to be returned in response to GET requests but not in response to HEAD requests. Could you point these status codes out to me? I can’t figure out which ones you might mean. best, Erik Hetzner ;; Erik Hetzner, California

Re: comments/feedback requested

can, then you don’t have a hierarchy. best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3 pgpCKCf52IfJJ.pgp Description: PGP signature

Re: comments/feedback requested

hierarchically’. This was an error. This sentence is referring to the entire URI, not just the path segment, so there are number of characters other than / in other parts of the URI which signify hierarchy. In the path part, however, only the / signifies hierarchy. best, Erik Hetzner ;; Erik Hetzner

Re: 404 from getRepresentation/handleGet?

you see the point about DELETE. Cheers to that. And thanks again for pointing it out. Adam p.s. My last message was jumbled. Sorry, I was tired. ;) p.p.s John, thanks for the great insights. I truly appreciated your messages. best, Erik Hetzner;; Erik Hetzner, California Digital

Re: comments/feedback requested

in latitude and longitude: | /Earth/37.0,-95.2. Use semicolons when the order doesn’t matter: | /color-blends/red;blue. best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3 pgpYkbgdaWE5M.pgp Description: PGP signature

Re: 404 from getRepresentation/handleGet?

. If we disagree about the definition, we’re not going to get very far. best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3 pgpOvbiLr7WDe.pgp Description: PGP signature

Re: comments/feedback requested

. Ultimately, it doesn't matter what your delimiter is. I just think slashes seem more intuitive for this type of ordered or hierarchical usage. It’s not commas vs. slashes: they have different meanings (according to the RWS book). best, Erik Hetzner ;; Erik Hetzner, California Digital

Re: 404 from getRepresentation/handleGet?

up with the resource in the same state (it doesn't mean all the responses are always identical). best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3 pgpWhyJeqsz8K.pgp Description: PGP signature

Re: 404 from getRepresentation/handleGet?

At Tue, 17 Jul 2007 20:56:48 -0600, Adam Taft [EMAIL PROTECTED] wrote: Erik Hetzner wrote: […] ‘idempotent’ means repeating the operation ends up with the resource in the same state (it doesn't mean all the responses are always identical). What we're saying is that _because_ the resource

Re: Setting Content-length in http client request?

. Thanks again for your help. And thanks as well for everybody’s work on Restlet. best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3 pgpKB0SdOUZyf.pgp Description: PGP signature

Setting Content-length in http client request?

up of an http client? best, Erik Hetzner ;; Erik Hetzner, California Digital Library ;; gnupg key id: 1024D/01DB07E3 pgpTR6oPWi61D.pgp Description: PGP signature