devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Keil <werner.k...@gmail.com>
Subject Fwd: [JIRA] (PORTLETSPEC3-63) Make user agent available to Portlets
Date Mon, 18 Apr 2016 10:25:54 GMT
User Agent will become a first class citizen of Portlet 3 API ;-)

Werner


---------- Forwarded message ----------
From: msnicklous (JIRA) <jira-no-reply@java.net>
Date: Mon, Apr 18, 2016 at 9:02 AM
Subject: [JIRA] (PORTLETSPEC3-63) Make user agent available to Portlets
To: issues@portletspec3.java.net



    [
https://java.net/jira/browse/PORTLETSPEC3-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=392093#comment-392093
]

msnicklous commented on PORTLETSPEC3-63:
----------------------------------------

Based on feedback from the EG, the implementation will be changed. Instead
of using the PortletRequest#getProperty() method, a new method will be
introduced to obtain the user agent string:
{code}
String PortletRequest#getUserAgent()
{code}
This will be more in line with the way other HTTP header information is
obtained through the portlet API.


> Make user agent available to Portlets
> -------------------------------------
>
>                 Key: PORTLETSPEC3-63
>                 URL: https://java.net/jira/browse/PORTLETSPEC3-63
>             Project: portletspec3
>          Issue Type: New Feature
>            Reporter: msnicklous
>            Assignee: msnicklous
>
> We should make  the use agent available to portlets in a standard manner.
The alternatives are:
> 1) Add the PortletRequest#getUserAgent() method and specify that it
always must return the user agent string.
> 2) Change the spec so that PortletRequest#getProperty("User-Agent")
always must return the user agent string.
> 3) Require support for the javax.ccpp.Profile that can be obtained
through:
> {code}
> Profile prof = (Profile)
((PortletRequest)request).getAttribute(PortletRequest.CCPP_PROFILE);
> Attribute attr = prof.getAttribute(deviceAttribute);
> {code}
> I think I would choose #2 unless there are opinions to the contrary.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message