You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2014/05/27 10:35:01 UTC
[jira] [Commented] (DELTASPIKE-613) Avoid windowhandler.html in GET
requests from links
[ https://issues.apache.org/jira/browse/DELTASPIKE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009493#comment-14009493 ]
Thomas Andraschko commented on DELTASPIKE-613:
----------------------------------------------
AFAICS it's a mix between LAZY and CLIENTWINDOW.
I have an similiar idea and already created a ticket: https://issues.apache.org/jira/browse/DELTASPIKE-570
The idea is to NOT render the dswid on the link but overwrite the onclick to lazy add the windowId and add a cookie.
So on a GET request, the server will check if a windowId and the cookie exists -> otherwise stream windowhandler.html.
Therefore if you do a "open in new tab" -> no windowId in the url, windowhandler will be streamed.
The streaming of the windowhandler is reduced to a minimum.
> Avoid windowhandler.html in GET requests from links
> ---------------------------------------------------
>
> Key: DELTASPIKE-613
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-613
> Project: DeltaSpike
> Issue Type: Improvement
> Components: JSF-Module
> Affects Versions: 0.7
> Reporter: Janario
> Assignee: Mark Struberg
> Attachments: dsrid_in_url.patch
>
>
> Some generated url could already detect the windowId and send with the first get avoiding windowhandler.html.
> In the actual model basically this are the steps from a click in a link:
> - Click in link (GET) to new page < Response windowhandler.html
> - windowhandler.html detect windowId by window.name and get page again adding dsrid and windowId in cookie
> So I suggest the detection of windowhandler.html be done before the first get avoing one more request.
> To this every urls should have a dsrid(could be equals as windowId) and the storeWindowTree function should also add the cookie, same as in windowhandler.html
> Clicking in a link the cookie will be generated and in server side read identifying the windowId
> To explain better I attatched a patch with some changes.
> Could anyone try this?
--
This message was sent by Atlassian JIRA
(v6.2#6252)