Yeah, I'm thinking Digest is the way I probably want to go. Sorry to 
hear that it's complicated. Do you have code anywhere that I could look 
at (just curious)?

Chas.

Tim Perrett wrote:
> Hey Chas,
> 
> I'm currently writing HTTP auth for lift, so watch this space :-)
> 
> It's unfortunatly pretty complex, so is taking longer than I'd hoped.  
> I'm impletmenting Basic and Digest auth; the latter being the most  
> secure.
> 
> Cheers, Tim
> 
> Sent from my iPhone
> 
> On 18 Nov 2008, at 02:21, "Charles F. Munat" <[EMAIL PROTECTED]> wrote:
> 
>> One thing I'm working on is a two-part application that involves a  
>> Lift
>> interface app and a REST CRUD back end. I plan to do the back end in
>> Lift as well.
>>
>> One reason for the separation is that it allows me to build other  
>> front
>> ends for the web service (a desktop app, something on the iPhone, an
>> Android app, etc.). Another reason is that the data model is pretty
>> complicated, and instantiating a lot of objects is not really  
>> necessary.
>> If I can handle the back end as just data, rather than objects,  
>> passing
>> it in and out using XML, that would be faster and easier, I think.  
>> And I
>> could use an XML database to store the data.
>>
>> A big issue, of course, is authentication and authorization. I'm
>> wondering if anyone else here is doing web services and if so how  
>> you're
>> handling authentication/authorization. Are you using Lift, or are you
>> handling it through the container. Can anyone talk about pros/cons of
>> the different methods? Suggestions?
>>
>> We're thinking about using Berkeley DB XML as the database. Anyone  
>> tried
>> that?
>>
>> Thanks.
>>
>> Chas.
>>
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to