On Sun, Nov 9, 2008 at 1:13 PM, Tim Perrett <[EMAIL PROTECTED]> wrote:
>
> Hey John,
>
> I take your point for sure - the only thing id say on this would be
> that there is argument (both for and against) of holding this type of
> resource representation in the request metadata as opposed to the
> concrete URI. Both ways are "restfull" as it were, id say its a matter
> of preference / use case. I need to check, but If you wanted to set
> the accept and content-type headers we have this partial function in
> lift rules:
I aggree on the preference part. I'm still curious towards the argument
though :)
> var determineContentType: PartialFunction[(Can[RequestState],
> Can[String]), String] = {
> case (_, Full(accept)) if this.useXhtmlMimeType &&
> accept.toLowerCase.contains("application/xhtml+xml") => "application/
> xhtml+xml"
> case _ => "text/html"
> }
Is that lowlevel Lift code or supposed to be how you use the API?
If it's the latter I think there's some improvements that can be done ;)
BR,
John
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
