Comments on: 3 Principles of Web Application (GUI) Design for the Command Line http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html Learn the UNIX/Linux command line Mon, 06 Jun 2011 01:35:32 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Brock Noland http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-5929 Brock Noland Thu, 10 Apr 2008 16:26:52 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-5929 Here's two: http://www.restlet.org/ http://simpleweb.sourceforge.net/ I personally <a href="http://abstractfinal.blogspot.com/2007/04/do-we-need-frameworks-for-rest.html" rel="nofollow">don't feel a framework is needed</a>. In fact, I shun frameworks in general as they create dependencies. Here’s two:

http://www.restlet.org/
http://simpleweb.sourceforge.net/

I personally don’t feel a framework is needed. In fact, I shun frameworks in general as they create dependencies.

]]> By: Noname http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-5904 Noname Thu, 10 Apr 2008 08:13:55 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-5904 A very good articale. As I understand there are numerous REST frameworks around , can you give examples? A very good articale.
As I understand there are numerous REST frameworks around , can you give examples?

]]> By: Perfomance testing - with curl http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-5796 Perfomance testing - with curl Tue, 08 Apr 2008 05:21:50 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-5796 [...] I need or want to do some type of performance testing. Given my ideas on software development, I can usually do this by making simple HTTP requests. I use curl for this. While you may be [...] [...] I need or want to do some type of performance testing. Given my ideas on software development, I can usually do this by making simple HTTP requests. I use curl for this. While you may be [...]

]]> By: Mac http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-4599 Mac Wed, 12 Mar 2008 02:17:05 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-4599 Very interesting. I'm not sure if you've seen this site, but I see a number of developers in my group referencing it. http://www.programmableweb.com/ Very interesting. I’m not sure if you’ve seen this site, but I see a number of developers in my group referencing it.

http://www.programmableweb.com/

]]> By: admin http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-4590 admin Tue, 11 Mar 2008 16:20:00 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-4590 Fixed title. Thanks Nino! Principals didn't feel right... Fixed title. Thanks Nino! Principals didn’t feel right…

]]> By: admin http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-4589 admin Tue, 11 Mar 2008 14:42:04 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-4589 My colleague just sent me this <a href="http://thoughtpad.net/alan-dean/http-headers-status.gif" rel="nofollow">image</a> which is <a href="http://thoughtpad.net/alan-dean/http-headers-status.html" rel="nofollow">an activity diagram to describe the resolution of HTTP response status codes</a>. Awesome. My colleague just sent me this image which is an activity diagram to describe the resolution of HTTP response status codes. Awesome.

]]> By: admin http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-4561 admin Tue, 11 Mar 2008 01:47:44 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-4561 David, Thanks for your comment! > Also most of REST supporting libraries and frameworks > don’t bother with much beyond basic auth, as cookie based > sessions are against REST principles. Basic Auth is not session based. I have created a <a href="http://bashcurescancer.com/basic-auth-example/" rel="nofollow">Basic Auth via PHP</a> example which shows this. Type any user and password and then add some query string to the URL, e.g.: ?a=b and you will notice your password is sent on every single request. > BTW REST is not just about GET, there are other verbs too: > you should use GET only for operations that just read data and > build a representation, if you want to add or change stuff use PUT > (or POST to create in most cases) and DELETE to, err, delete them. > A good REST app can be driven from the command line. I am in 100% agreement. I am not describing how to implement <a href="http://www.xfront.com/REST-Web-Services.html" rel="nofollow">REST</a>. I am giving basics that help me use your application from the command line. I agree, a fully compliant REST application would be ideal. Brock David,

Thanks for your comment!

> Also most of REST supporting libraries and frameworks
> don’t bother with much beyond basic auth, as cookie based
> sessions are against REST principles.

Basic Auth is not session based. I have created a Basic Auth via PHP example which shows this. Type any user and password and then add some query string to the URL, e.g.: ?a=b and you will notice your password is sent on every single request.

> BTW REST is not just about GET, there are other verbs too:
> you should use GET only for operations that just read data and
> build a representation, if you want to add or change stuff use PUT
> (or POST to create in most cases) and DELETE to, err, delete them.
> A good REST app can be driven from the command line.

I am in 100% agreement. I am not describing how to implement REST. I am giving basics that help me use your application from the command line. I agree, a fully compliant REST application would be ideal.

Brock

]]> By: Daniel Yokomizo http://bashcurescancer.com/3-principles-of-web-application-design-for-the-command-line.html/comment-page-1#comment-4559 Daniel Yokomizo Tue, 11 Mar 2008 01:28:42 +0000 http://bashcurescancer.com/3-principals-of-web-application-design-for-the-command-line.html#comment-4559 Instead of three points you can just say REST and get away with it. Point 1 is basic in REST, as it supports different representations via Accept* headers. It's usual to just send a request for xml or json or even csv representations of something that's also represented as html and get those. Also most of REST supporting libraries and frameworks don't bother with much beyond basic auth, as cookie based sessions are against REST principles. BTW REST is not just about GET, there are other verbs too: you should use GET only for operations that just read data and build a representation, if you want to add or change stuff use PUT (or POST to create in most cases) and DELETE to, err, delete them. A good REST app can be driven from the command line. Instead of three points you can just say REST and get away with it. Point 1 is basic in REST, as it supports different representations via Accept* headers. It’s usual to just send a request for xml or json or even csv representations of something that’s also represented as html and get those. Also most of REST supporting libraries and frameworks don’t bother with much beyond basic auth, as cookie based sessions are against REST principles. BTW REST is not just about GET, there are other verbs too: you should use GET only for operations that just read data and build a representation, if you want to add or change stuff use PUT (or POST to create in most cases) and DELETE to, err, delete them. A good REST app can be driven from the command line.

]]>