Thanks. This is good. Does the device registry list a regexp to match
against the User-Agent? (It probably should, and ordering of the
registry would then be important.)
On 07/08/2011 08:48 PM, shelan Perera wrote:
Hi Anil,
On Sat, Jul 9, 2011 at 7:31 AM, Anil Gangolli<[email protected]> wrote:
I do like the idea of generalizing so that it isn't "standard" vs. "mobile"
but type-based. I'm still confused about how a given request is supposed
to be associated with a given theme type. Is it some form of
auto-detection, or the request comes in on a different URL for mobile?
Will this be pluggable?
We use request header user-agent to identify the request whether it is
coming from a mobile or a standard device. (We have a device repository
maintained to match against).And the we render mobile or templates
accordingly.So in page , Search ,Feed servlets etc. logically render the
correct template.There is no change in the url but when you view in a device
it will auto detect.
Thanks
--a.
On 7/8/2011 1:38 PM, Dave wrote:
Since the mid-term eval is coming up, I did an in-depth review of the
Roller Mobile design and ongoing implementation.
https://cwiki.apache.org/**confluence/x/VYWoAQ<https://cwiki.apache.org/confluence/x/VYWoAQ>
I hope to have a patch this weekend that adds the two new tables and
objects that I am recommending in the design.
Thanks,
- Dave
