Re: IBM i authentication and RESTful web service design

I suppose we could go with Rest-ful, Pre-rest or No-Rest then unless someone can think of anything better.

HTTP API is another useful descriptor that I used to use. 

Roy should be glad he got credit for inventing the term.  Now the rest of us can frustrate him. Or make him Rest-Less :-)

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx 
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

-----Original Message-----
@Richard,

Roy Fielding expressed a great deal of frustration with people hijacking
his acronym (REST) to describe their various web services APIs and
protocols. He suggested that people come up with their own acronyms.
Otherwise, why go to the bother of categorizing and articulating 6 key
architectural constraints in a thesis?

Roy made a point, saying that PROCESSES come and go, but DATA remains, and
REST is about accessing DATA; A little pedantic, perhaps. But he created
the SPEC.