happy new year
andy
--
You received this message because you are subscribed to the Google Groups "ObjectiveResource" group.
To post to this group, send email to objectiv...@googlegroups.com.
To unsubscribe from this group, send email to objectiveresou...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/objectiveresource?hl=en.
Generally, User creation works by RESTfully creating a User.
You can check credentials by RESTfully creating a UserSession.
You can use HTTP Basic Auth after that.
The sample code for Authlogic needs some additional respond_to blocks
to work well with ObjectiveResource. In particular, you probably want
to replace some of the redirect logic with xml renders of various
objects or errors.
--Corprew
how exactly are you doing that? I am facing the same task currently
and I am wondering
how one would go about to authenticate a user based on a login and a
password.
Could you send me a snippet maybe on how you did this? The way I see
it I have the problem
that not only need I to authenticate once but to save the auth token
from the rails app for that user
to authenticate the subsequent requests as well.
greetz
Rob
On 3 Jan., 00:10, Zeitgeist <corp...@gmail.com> wrote:
> I use it in a few apps, and it works well for me.
>
> Generally, User creation works by RESTfully creating a User.
> You can check credentials by RESTfully creating a UserSession.
> You can use HTTP Basic Auth after that.
>
> The sample code for Authlogic needs some additional respond_to blocks
> to work well with ObjectiveResource. In particular, you probably want
> to replace some of the redirect logic with xml renders of various
> objects or errors.
>
> --Corprew
>