>
> HATEOAS/REST is resilience over efficiency, aka, long term
> over short term design to achieve stability or, why scale
> matters.
That is true.
> Let the client look at the document and decide
> instead of the server dishing a header.
The client sometimes needs help from its user and from the server, apart and aside from
headers, to determine what the next state should be. Hence the hypermedia affordances.
>
> On the other hand, sometimes it is worth throwing all the
> pieces in the air and breaking it to achieve innovation
> through original perspective.
Don't do that! It's just a flip of a bit that needs doing here. If we can
we agree on that, we can proceed to discuss next steps. But I think
step one is to review how to achieve RESTful XML at Web scale.
> That's what I do if I get stuck in a musical composition that
> starts to bore me or goes to gray goo. That is the joy of
> anonymity and
> independence: being one's own client means never having to
> serve up "I'm sorry: 404".
Beautiful! But here I am showing how stupid I am in public. Hopefully,
Roy's right, and I've not misunderstood him.
I think both are true, but hey, I've been wrong before!! :-)
Peter
>
> len
>
> -----Original Message-----
> From: Rushforth, Peter [mailto:]
> Sent: Tuesday, July 03, 2012 1:37 PM
> To: ; Len Bullard
> Cc: David Carlisle;
> Subject: RE: [xml-dev] "Introducing MicroXML, Part 1: Explore
> the basic principles of MicroXML"
>
>
> > That is HATEOAS.
>
> Sorry, that is code-on-demand, and either js or XSLT can implement
> HATEOAS now,
> especially the XML stuff with XSLT, because it is easy.
>
> Peter
>
