http://apps.new.facebook.com/birthday/

And a test app that looks like this:

http://apps.new.facebook.com/test-birthday/

And you’re going to have callback urls of

http://myserver.somedomain.com/facebook-apps/birthday/
http://myserver.somedomain.com:8080/fb-birthday-test/

Or whatever.

You’ll find (especially when you start dealing with uploading images, etc.) that you need these full urls in a few places in your templates. Places you don’t think they OUGHT be to needed. Make sure you’re using template variables for that, so that you can manage your test server and your real server with the same codebase, and so that you don’t have to remember to flip a switch somewhere before you commit your code every time. The config file should be svn-ignore (or equivalent in git, or whatever your favorite revision-control-system is today).

If you’re making pretty RESTian interfaces to your apps, you’re still going to have a bunch of /object/controller/action/param-type stuff that goes on the end of these paths. Which is, obviously, fine.

Joshua

No, you can keep all the data in a single database. But you’re going to need at least a couple of extra fields for each user, and it’s probably simpler to define a new table and join them – this is to keep the session keys for each user, so that you can update their profile data while they’re not on your application page.

Let me add some stuff that I think might be critical.

1. If you have a shared host. Do your entire app in ajax so you can slowly load your app. Facebook time out is 8secs and some Hosting services can’t return in that time. This will minimize if not eliminate the screen of death, called Response Time.

2.And if you are running dedicated hosting try doing preload fql. The fql statements take up tons of time to do.