You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by keyvanmod <ke...@hotmail.com> on 2008/04/15 14:52:36 UTC
Jetspeed UserAgent Switching ...
Is this how the jetspeed useragent should be working?
We have added several new rows to the CLIENT table. A row on the MEDIA_TYPE
table has also been added for each row added on the CLIENT table. These rows
are linked to a MIMETYPE, using the PREFERRED_MIMETYPE_ID column. The
MIMETYPE is the linked to the MEDIA_TYPE table through the
MEDIATYPE_TO_MIMETYPE table.
Should there be a MIMETYPE 1 -> 1 MEDIATYPE relationship or a MIMETYPE * ->
1 MEDIATYPE relationship. We discovered that a MIMETYPE * -> 1 MEDIATYPE
relationship would produce inconsistent results it would simply result in
the first MEDIATYPE being returned. Is there any kind of ordering system
involved here
We are not sure exactly how the CapabilityCustomizerValveImpl in Jetspeed
2.1.3 should be working. If all the mediatypes being returned are not passed
to the constructor of the CapabilityCustomizerValveImpl valve, the default
media type will be used.
Can anyone shed any light on the above observations and say whether this is
the correct method for this system to be used?
--
View this message in context: http://www.nabble.com/Jetspeed-UserAgent-Switching-...-tp16700356p16700356.html
Sent from the Jetspeed - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Jetspeed UserAgent Switching ...
Posted by Woonsan Ko <wo...@yahoo.com>.
Jetspeed-2.1.3 has a problem in selecting right MEDIATYPE on a client User-Agent as you observed.
I think we need to improve it because it's not clear why we have to go from client -> mimetype ->
mediatype. ( See David's comment for detail:
http://www.nabble.com/Supporting-Pocket-PC-td12400648.html )
CapabilityCustomizerValveImpl in Jetspeed-2.1.3 can be a solution here.
If you put entries with client name key and mediatype name value, then it overrides the mediatype
for the client.
For example, if you add capabilityCustomizerValve after capabilityValve, then Pocket IE client's
mediatype is set to 'html-basic', not to 'html' though Pocket IE has same preferred mime type,
'text/html'.
Therefore, if you want to support other mediatypes for some clients having same preferred mime
type, then add entries to the map as a second constructor-arg of capabilityCustomizerValve in
pipelines.xml accordingly after adding rows to CLIENT and MEDIA_TYPE table.
Also, the capabilityCustomizerValve should be located after capabilityValve.
Regards,
Woonsan
--- keyvanmod <ke...@hotmail.com> wrote:
>
> Is this how the jetspeed useragent should be working?
>
> We have added several new rows to the CLIENT table. A row on the MEDIA_TYPE
> table has also been added for each row added on the CLIENT table. These rows
> are linked to a MIMETYPE, using the PREFERRED_MIMETYPE_ID column. The
> MIMETYPE is the linked to the MEDIA_TYPE table through the
> MEDIATYPE_TO_MIMETYPE table.
>
> Should there be a MIMETYPE 1 -> 1 MEDIATYPE relationship or a MIMETYPE * ->
> 1 MEDIATYPE relationship. We discovered that a MIMETYPE * -> 1 MEDIATYPE
> relationship would produce inconsistent results it would simply result in
> the first MEDIATYPE being returned. Is there any kind of ordering system
> involved here
>
>
> We are not sure exactly how the CapabilityCustomizerValveImpl in Jetspeed
> 2.1.3 should be working. If all the mediatypes being returned are not passed
> to the constructor of the CapabilityCustomizerValveImpl valve, the default
> media type will be used.
>
> Can anyone shed any light on the above observations and say whether this is
> the correct method for this system to be used?
> --
> View this message in context:
> http://www.nabble.com/Jetspeed-UserAgent-Switching-...-tp16700356p16700356.html
> Sent from the Jetspeed - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org