[
http://jira.magnolia.info/browse/MAGNOLIA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805#action_17805
]
Giancarlo Berner commented on MAGNOLIA-2343:
--------------------------------------------
We also use selectors a lot, especially in combination with Base64 encoding.
One important reason is caching: While requests with parameters are not
returned from cache (e.g. Web servers), requests with selectors are. So if e.g.
a user iterates through an image gallery, these images would be cached.
Another problem when removing selectors are the existing projects. It would
indeed be very cumbersome to rework each and every project.
As Ralf and Wolfgang are asking, I am very curious too to get the idea why you
want to remove selectors.
> Selectors can be deprecated, virtual uri mappings can do a better job
> ---------------------------------------------------------------------
>
> Key: MAGNOLIA-2343
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2343
> Project: Magnolia
> Issue Type: Task
> Components: core, templating
> Reporter: Gregory Joseph
> Assignee: Gregory Joseph
> Fix For: 3.6.2
>
> Attachments: Picture 1.png
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
