... Note that this is a feature of the DNS configuration. It's not always the case. -- Nic Ferrier http://www.tapsellferrier.co.uk for all your tapsell...
Yeah, POST is the protocol equivalent pointing at something and grunting at someone. Who knows what will happen in that language game [1]. What you do know is...
... See my point elsewhere about APP. It introduces these kinds of side-effects, but in a predictable fashion. You can't always work with a collection/iterator...
... Except for the grunting part, yes. The entity in a POST can be a lot more elaborate and formal (and therefore more expressive) than a grunt, though....
... It's still grunting. Elaborate here would means two fingers. ... Apply Grice's maxims. Don't grunt when you have a better way of saying things. ... What...
... The hypothesis is that all constraints are expressible as a separation of concerns, and therefore that all architectural properties derive from some form...
... When I read that blog post about RESTafarians, and when you start this response with "now Bill, no need to get defensive", I'm not sure what to think about...
... Referring to the dissertation, I see Roy identifies separation of concerns as the principle behind the client-server constraint. How would you express the...
... Fascinating indeed. Here's a potential counterexample: a latency constraint. Suppose a protocol coupling two components imposes a severe latency...
... Statelessness separates message semantics from server state. ... You stumped me. Come to think of it, even self-description in general isn't expressible...
Hi Teo, ... That's an excellent question, and one I've wondered about as well. My answer (as usual) is "it depends" -- on what you mean by "service". If you...
... Hmm....I had no idea that phrase did not exist already...felt so natural. Sorry. I mean a constraint that applies to the application semantics of a system....
... Hmm, I'm not sure that term makes sense. Constraints are on data, components, and connectors, which are all "application layer" AFAICT. Can you give an...
Bill, I once had an unaltered tomcat as a pet who hunted quite well and on more than one occasion POSTed a dead rabbit on my back doorstep. He didn't use...
... Ok, seems like I was trying to point out a distinction that inherently has been made already by focusing on connector, component and data. So, using your...
... Let's try the other way round: does SOA (or WS-*) use any constraint on any of those three? I'd say 'no'. Does WS-*'s constraining the data to SOAP count...
... This sounds like what I was trying to say, but let's check: what do you mean by 'ad hoc REST' and in what way do you think Atom constrains it? Jan...
... I don't think they are. I think all of my previous comments about "general" constraints (whether application level or "transport" level) being the key to...
... It's hard to tell for certain of course, since SOA isn't defined. But if you look at what people are doing in its name, you can pick out at least a couple...
Nice try. The rabbit's not a communication act, it's an indexical - you infer in passing the tomcat left the rabbit - it's not as though the tomcat told you it...
Of course not, the rabbit is the entity. But I can see this is going nowhere. Did you have a point to make about POST being degenerate (whatever you mean by...
... case. What would be the DNS configuration option that would disable this, and can it be controlled by the authoritative DNS? Also, is the existence of...
... Depends on the server of course. It's about how the names are resolved... not the policy of the zone. ... I don't think a server is required to implement...
... I think it is. HTTP without POST is an interesting gedanken experiment. It's like having English without "just do it". POST is uniformly devoid of meaning;...
