(public).sospep.events ~ view task ~ CREATE-article-get-vs-post

<h1 style="text-align: center;">title</h1>
<h2>[previously]</h2>
<ol>
<li><strong>] send form methods&nbsp;</strong></li>
<ol>
<li>]&nbsp;</li>
</ol>
<li><strong>] get</strong></li>
<ol>
<li>] default method</li>
<li>] passes form data(querystring) in url,&nbsp;</li>
<li>] use GET for 'safe' actions</li>
<li><strong>] more usable b/c&nbsp;</strong></li>
<ol>
<li>] cacheable - browsers can cache</li>
<li>] history - browser can maintain history of pages retrieved with get</li>
<li>] bookmarkable -&nbsp;</li>
<li>] distributable - can share (email, social, etc) links with&nbsp;</li>
<li>] hackable - as in you can 'predict' what view/articles/2012, could be changes to&nbsp;view/articles/2013, /2011, etc depending on the sites</li>
</ol>
<li>* COMMENTer Vincent Robert -I think REST describes it right. GET is only about URIs, it is about getting the representation of a resource identified by a URI. Now some prefer pretty URIs but using query variables is perfectly legal in HTTP.</li>
</ol>
<li><strong>] post</strong></li>
<ol>
<li>] use post for 'unsafe' actions</li>
<li>] passes querystring data in body of post (more secure)</li>
<li>] sends form input&nbsp;</li>
<li>] browser must implement repeat WARNING IF resending</li>
<li>] use for submitting sensitive data,&nbsp;</li>
<li>] &gt; length ( vs 4kb)&nbsp;</li>
<li>* COMMENTer Vincent Robert POST is about processing. It is about sending content to a resource for processing. Again, this resource can have a URI using query variables.</li>
</ol></ol>
<h2>[currently]</h2>
<ol>
<li>] &nbsp;</li>
</ol>
<h2>[next]</h2>
<ol>
<li>] REFERENCE</li>
<ol>
<li><a href="http://blog.teamtreehouse.com/the-definitive-guide-to-get-vs-post" target="_blank">The Definitive Guide to GET vs POST - Treehouse Blog</a></li>
</ol></ol>

~ view task ~ TaskGroup] any-all FROM [ Plan] planning-project IN [ calendars] technology-developer-www