mikek85

Apparently this makes things easier if/when you come to distribute shares to others as it will be a simple allocation of unallocated shares rather than a more convoluted 'transfer' process.

I should've clarified no limit. This article is presumably talking about no limit - since that is by far the predominant game.

With all due respect, you have a poor understanding of poker if you really think there is a way to "memorize the correct action for every scenario". Poker is about interaction, spotaneity, 'feel', instinct. Mastering those things is where to get a real edge, not math - particularly in no limit. Hence my comment.

isn't bad

edit: Btw, any well designed website is at level 3.

^ it's tiny, easily the best book I've ever read.

1. use hyperlinks and link relations i.e. <link href="/people/bob" rel="friend" />

2. don't bother with multiple media types (unless /absolutely/ necessary) . If appropriate try to use/extend an established type such as Atom/AtomPub

3. make sure you set your cache control headers appropriately

:)

.. plaaaayaaaaa

Idea 2 is the way to go because it's resource oriented and you get useful stuff like 405's for free which you don't with the sinatra approach.

Please don't remove routing. Having routes is important - it makes the code more descriptive and easier to follow. All a route needs to do is map one URI pattern to one controller, i.e:

/blog -> BlogController

/blog/:post -> BlogPostController

/blog/:post/comments -> BlogPostCommentsController

I wrote a hack for Zend Framework last year to prove how this would work:

http://restafari.blogspot.com/2010/04/restful-php-applicatio...