REST with Rails: Registration Now Open

Posted by jeff Sunday, August 10, 2008 14:53:00 GMT

Registration is officially now open for REST with Rails, coming to Austin, Texas on Saturday, October 4, 2008.

REST with Rails

When: Saturday, October 4, 2008, 8:30am – 5:00pm

Where: FiveRuns Offices: 209 West 9th Street, Suite 100, Austin, Texas 78701

Cost: $295.00

If you’re new to REST and want to learn what all the fuss is about, join us for a fun, one-day workshop! We’ll cover all the basics of RESTful development with Rails. This class is geared for those new to REST, regardless of how long you’ve been using Rails. (We assume you can at least create a simple Rails app, but not much more than that.)

All of our workshops have a friendly atmosphere. There really are no dumb questions. We use an informative combination of slides and live coding demos instead of long, boring powerpoint presentations.

And, thanks to FiveRuns, this public workshop will be held at their brand new offices in downtown Austin, Texas!

Seating is quite limited, so read all about it and then sign up!

(Those who signed up for early notification should have received your discount code. If for some reason you didn’t get it, please let us know.)

Thanks, and we hope to see you there!

Comments

Leave a response

  1. ruby on rails developer   August 12, 2008 @ 03:30 PM

    I think one of the biggest questions I have with the rest approach is, when is it okay to split a request into a new action/method, and when is it best handled by a case statement within update/create. It seems many people get caught up with the idea that ALL POSTs have to go to create, and ALL PUTs have to go to update… when it’s more important to ensure you’re using the right verb for the method you’re calling.

  2. Jeff   August 12, 2008 @ 06:35 PM

    Thanks for the question. Generally, it’s best to stick with the seven pre-routed actions that Rails provides. Once in a blue moon you might need a custom action, and that’s fine when it’s necessary.

    However, the need for a custom action often hints at an as-yet undiscovered resource. This is one of the topics we’ll be covering in the workshop.