Re: IBM i authentication and RESTful web service design

BTW Nathan, I think there's some validity to arguments that that REST is for simpler web services and the WS-* standards are for more complex web services. REST architectural constraints don't make clear how to handle things like security, transactions, and QoS when web services are distributed across multiple servers. The WS-* standards do (at least that's my understanding having never used them). 

There are some books that supposedly address these limitations of REST (e.g., "SOA with REST: Principles, Patterns, & Constraints for Building Enterprise Solutions with REST"). I own this particular book but haven't cracked it open yet. There's only so many hours in a day...

I anticipate most of our iSeries COBOL developers would develop smaller, simpler web applications aimed primarily at our employees within particular lines of business. Our first attempts will almost certainly be smaller and simpler so we can gain experience and build on successes. REST seems like a good starting point. We might well end up using the WS-* standards for more complex applications in the future. Never say never. 

Thanks,
Kelly


-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, May 14, 2015 1:31 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] IBM i authentication and RESTful web service design

Kelly,

Regarding additional resources, I have begun documenting our web portal. It is far from complete. Most of the hyperlinks are just placeholders for future use. The URL is a temporary address. But the "Introduction" section has content which is geared toward developers. Feel free to peruse.

http://www.radile.com:9220/rdweb/info/home.html?page=ptl/intro/intro.html&toc=ptl/toc.html

Based on previous conversations, some may be confused by your use of the term "web services". My understanding is that you're interested in developing "web applications", having browser user interfaces.

As "web applications" grow in complexity, how and where you manage state, and particularly whether you manage state on the client or the server is an important architectural consideration.

For complex applications which support browser user interfaces, it is better to manage state on the server, in my opinion.

The Fielding dissertation on REST, is geared toward simple (basic) services for non-browser clients.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.