StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PORuby 1.9.2 + Sinatra - Requiring authentication on certain routes
primarykey
Id
7876004
data
AcceptedAnswerId
7876476
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-24T13:00:59.213
FavoriteCount
3
LastActivityDate
2011-10-27T08:47:30.790
LastEditDate
LastEditorUserId
0
OwnerUserId
476660
ParentId
0
PostTypeId
1
Score
0
ViewCount
1550
LastEditorDisplayName
text
Body
Before I begin, this is basically a port of an existing ASP.MVC REST style service to Sinatra. I am fairly new to Ruby so dont really know the best practises yet, and the web seems a bit torn on the subject. So currently in the ASP flavour we have some controllers like so: <pre><code>public class MyController : Controller { [Authenticate] public ActionResult AccessSecretStuffs() {...} public ActionResult AccessPublicStuffs() {...} } </code></pre> Now we use a filter to make sure that any actions with Authenticate check for authentication from the current user before loading the action. The routes setup for these are fairly vanilla, they just map to the controller and actions. Now in Ruby land using Sinatra you dont tend to have controllers, everything is an action, and as we are purely looking to expose data in a restful way this seems great. However I need to be able to make sure that whenever certain routes are called with Sinatra that it will basically call a bit of code first to check if they can access the action, then if not redirect them to the login page. I was thinking of just putting in some AOP to cover this, but after a bit of reading everyone says Ruby doesnt need AOP and already provides most of the functionality out of the box. So can anyone shed some light on the best practise for doing this? Sinatra documentation has a before method that would be applicable, but then I would need to do a before method for every other route method, which isnt ideal. In my mind I just want to declare a route, and then put some sort of annotation/attribute at the end which indicates that something needs to happen... Hope that makes some sort of sense :)
Tags
<ruby><authentication><sinatra><aop>
Title
Ruby 1.9.2 + Sinatra - Requiring authentication on certain routes
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGrofit
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PORuby 1.9.2 + Sinatra - Requiring authentication on certain routes
 UserUserId
 USAlex R
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 PORuby 1.9.2 + Sinatra - Requiring authentication on certain routes
 UserUserId
 USMarvin Alejandro Herrera
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.