That looks like it might just be what I needed - THX :) On Feb 20, 11:54 am, Nikita Kovshov <[email protected]> wrote: > Hi, > > you can use mod_rewrite module for Apache: > beginner's guide -http://articles.sitepoint.com/article/guide-url-rewriting > essential guide -http://httpd.apache.org/docs/current/mod/mod_rewrite.html > > On Feb 20, 10:24 pm, craigpierce <[email protected]> wrote: > > > Hello All - > > > I'll try to keep this brief - I'm sure the answer is simple but I just > > don't get it... > > > I'm looking to build a simple API similar to Twitter's (I don't care > > whether it's actually considered RESTful or not - I'm just calling it > > that), but there is one thing that NO ONE explains: how the *actual* > > folder structure works... > > > Example: > > >http://www.url.com/api/user/123/ > > > Let's say that's my URL to get user info for user ID '123'; does there > > need to be a folder called 'api' with a folder called 'user' with a > > folder for each and every user ID, each with its own index.php file in > > it that returns that user's data? Surely not (especially when you're > > Twitter with 100 million users and billions of tweets to deal with), > > but how else could this work? > > > Thanks so much - sorry for the OT thread...
-- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
