rest/rails - Revision history

Sknebel: Undo revision 66586 by Irisp (Talk)

2017-10-11T13:43:45Z

Undo revision 66586 by Irisp (Talk)

← Older revision		Revision as of 13:43, 11 October 2017
Line 74:		Line 74:
	string and have the values funneled into the same		string and have the values funneled into the same
	parameters -- your controller wouldn't care where		parameters -- your controller wouldn't care where
	the data is come from. I realize yaml ~~[https://codebeautify.org/yaml-validator Yaml lint]~~ is supported		the data is come from. I realize yaml is supported
	by rails natively, but it should be possible to		by rails natively, but it should be possible to
	register handlers for any other mime types.		register handlers for any other mime types.

Irisp at 13:43, 11 October 2017

2017-10-11T13:43:14Z

← Older revision		Revision as of 13:43, 11 October 2017
Line 74:		Line 74:
	string and have the values funneled into the same		string and have the values funneled into the same
	parameters -- your controller wouldn't care where		parameters -- your controller wouldn't care where
	the data is come from. I realize yaml is supported		the data is come from. I realize yaml [https://codebeautify.org/yaml-validator Yaml lint] is supported
	by rails natively, but it should be possible to		by rails natively, but it should be possible to
	register handlers for any other mime types.		register handlers for any other mime types.

BradGessler at 18:31, 15 October 2007

2007-10-15T18:31:19Z

← Older revision		Revision as of 18:31, 15 October 2007
Line 1:		Line 1:
			<div style="border: 1px solid #069; padding: 1em; margin: 1em 0;">'''All of the old stuff in this article that has been implemented in Rails has been cleaned out. This article should NOT be considered obsolete.'''</div>
	= Participants =		= Participants =
	* David Hansson		* David Hansson

BradGessler at 18:29, 15 October 2007

2007-10-15T18:29:31Z

@@ Line 1: / Line 1: @@
 = Participants =
 * David Hansson
@@ Line 10: / Line 4: @@
 * Ernest Prabhakar
 * [http://www.bradgessler.com/ Brad Gessler]
 = Wish List =

BradGessler: /* Filtering */

2007-10-14T17:29:15Z

Filtering

← Older revision		Revision as of 17:29, 14 October 2007
Line 350:		Line 350:

	Also, for the case of "Autocomplete" lists, the JSON or XML may have to be embedded into some sort of HTML template so that the list can be styled appropriately. These might be specified as templates, which are proposed above.		Also, for the case of "Autocomplete" lists, the JSON or XML may have to be embedded into some sort of HTML template so that the list can be styled appropriately. These might be specified as templates, which are proposed above.

			== Globaly Unique XML/JSON ID ==
			Currently in RESTful rails, the IDs of XML/JSON objects are the IDs as they appear in the database. For example,

			<pre>
			<poll>
			<created-at type="datetime">2007-07-02T11:13:46-07:00</created-at>
			<id type="integer">29</id>
			<multivote type="boolean">false</multivote>
			<permalink>LTMxNDk5MTc2MQ</permalink>
			<question>What Would Tyler Durdon Do?</question>
			<updated-at type="datetime">2007-10-08T13:53:11-07:00</updated-at>
			<user-id type="integer">1</user-id>
			<is-open type="boolean">false</is-open>
			<total-results-count type="integer">1</total-results-count>
			</poll>
			</pre>

			The ID should instead refer to the globally unique HTTP location of the resource, not its primary key ID in the database. The above representation should instead appear as:

			<pre>
			<poll href="http://www.polleverywhere.com/polls/LTMxNDk5MTc2MQ.xml">
			<created-at type="datetime">2007-07-02T11:13:46-07:00</created-at>
			<multivote type="boolean">false</multivote>
			<question>What Would Tyler Durdon Do?</question>
			<updated-at type="datetime">2007-10-08T13:53:11-07:00</updated-at>
			<user-id type="integer">1</user-id>
			<is-open type="boolean">false</is-open>
			<total-results-count type="integer">1</total-results-count>
			</poll>
			</pre>

			Note the ''href'' is the unique identifier for the poll. This would be advantageous when displaying a list of larger datasets. The list could contain many href to the more complete representations. The client could then directly follow the URL rather than placing the burden of URL construction on the consuming application. Also, this makes the possibility of breaking the client side application less likely since it doesn't have to understand how to plug the ID column into a URL; instead, it can just directly access the URL.

	== Examples (TBD) ==		== Examples (TBD) ==

BradGessler: /* Participants */

2007-10-14T17:22:24Z

Participants

← Older revision		Revision as of 17:22, 14 October 2007
Line 9:		Line 9:
	* Dan Kubb		* Dan Kubb
	* Ernest Prabhakar		* Ernest Prabhakar
	*		* [http://www.bradgessler.com/ Brad Gessler]

	= Plug-ins =		= Plug-ins =

BradGessler: /* Filtering */

2007-10-14T17:15:24Z

Filtering

← Older revision		Revision as of 17:15, 14 October 2007
Line 348:		Line 348:

	Some of these may be a bit too 'database' specific, so I would be interested in finding the right nomenclature to generalize this a bit more.		Some of these may be a bit too 'database' specific, so I would be interested in finding the right nomenclature to generalize this a bit more.

			Also, for the case of "Autocomplete" lists, the JSON or XML may have to be embedded into some sort of HTML template so that the list can be styled appropriately. These might be specified as templates, which are proposed above.

	== Examples (TBD) ==		== Examples (TBD) ==

BradGessler at 17:13, 14 October 2007

2007-10-14T17:13:37Z

Show changes

JohnWheeler: /* Simply RESTful */

2007-10-08T03:03:58Z

Simply RESTful

← Older revision		Revision as of 03:03, 8 October 2007
Line 63:		Line 63:
	While this URL structure is somewhat unusual, it is still RESTful in that they would be embedded as links in the hypermedia, and thus don't actually violate [[rest/opacity]] constraints.		While this URL structure is somewhat unusual, it is still RESTful in that they would be embedded as links in the hypermedia, and thus don't actually violate [[rest/opacity]] constraints.

	Similarly, we cope with browser limitations by embedding a hidden "_method=DELETE" ~~paramater~~ in forms for the delete button, which the server should synonomize to "DELETE" as used by more full-featured clients.		Similarly, we cope with browser limitations by embedding a hidden "_method=DELETE" parameter in forms for the delete button, which the server should synonomize to "DELETE" as used by more full-featured clients.

	== RESTful Rails ==		== RESTful Rails ==

DrErnie at 21:25, 20 February 2007

2007-02-20T21:25:41Z

← Older revision		Revision as of 21:25, 20 February 2007
Line 1:		Line 1:
	'''This Page Is Obsolete'''		'''This Page Is Obsolete'''
	This is now mostly obsolete, as the concepts have been implemented as part of Rails 1.2.
			This is now mostly obsolete, as the concepts discussed below have pretty much all been implemented as part of Rails 1.2's scaffold_resource.

	For more information, see the [http://www.b-simple.de/documents RESTful Rails Development] Guide.		For more information, see the [http://www.b-simple.de/documents RESTful Rails Development] Guide.