On Mar 16, 2013, at 3:30 PM, Jonathan Christensen <[email protected]> wrote:

> I'm looking for some advice. I'm building an iOS application that does the 
> typical things that iOS applications do: talk to a rest api to get things 
> like user generated photos and info, and allow users to register and login 
> and submit photos and other information. Imagine essentially the same api 
> that instagram would have.
> 
> I know (knew) rails well but it's been about a year since I did my last rails 
> app. I was actually considering doing this in Node, but there are some 
> limitations node has around server side intensive processing that I knew we 
> would hit eventually.
> 
> So, I'm back to Rails. My question is, where do I go to figure out how people 
> are starting new rails apps these days? What versions of ruby/rails should I 
> use? It used to be you just did 'rails <name of your project>' and then built 
> scaffolds and deleted a bunch of files. But I don't need a web app, and 
> there's probably some Rest API bootstrapper or something out there...
> 
> What do you think? Anything I should take a look at?
> Thanks,
> —Jon

One thing: do yourself a favor and just use UUIDs as primary keys throughout 
your database.

If you’re using Postgres (and you should), there is a standard extension that 
adds a function for generating UUIDs, so you can just set a call to that 
function as your default value for your primary keys.

Make sure you use a good library (almost certainly based on window.crypto if 
it’s Javascript) in any web apps (or, say, Phonegap) to generate your UUIDs.

Basically, UUIDs make synchronization and idempotency mostly pretty simple. (If 
you don’t know what idempotency is, make sure you look that up).

-- 
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--- 
You received this message because you are subscribed to the Google Groups "SD 
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to