You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/10/02 16:39:50 UTC

[jira] Created: (TAPESTRY-1797) Mechanism to send pointers to serialized data to the client, not the data itself

Mechanism to send pointers to serialized data to the client, not the data itself
--------------------------------------------------------------------------------

                 Key: TAPESTRY-1797
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1797
             Project: Tapestry
          Issue Type: New Feature
          Components: tapestry-core
    Affects Versions: 5.0.5
            Reporter: Howard M. Lewis Ship


Tapestry has the capability to store much data on the client, whether it is persisted page fields, or Form component action data.  This presents a couple of problems; first, it inflates the size of the rendered HTML stream.  Second, it is a potential security issue, since a hyper-intelligent black hat might find a way to change such data before returning it.

What if Tapestry stored the associated bytestreams on the server, and provided, in the HTML, just a relatively short pointer (a string id that points to the correct bytestream) to the stream?

A small amount of additional data on the server side could be used to authenticate the pointer, using the user's session id (if a session exists) and host ip.

Unreferenced data would be periodically purged.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-1797) Mechanism to send pointers to serialized data to the client, not the data itself

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-1797:
-------------------------------------------

    Fix Version/s: 5.1

> Mechanism to send pointers to serialized data to the client, not the data itself
> --------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1797
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1797
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.1
>
>
> Tapestry has the capability to store much data on the client, whether it is persisted page fields, or Form component action data.  This presents a couple of problems; first, it inflates the size of the rendered HTML stream.  Second, it is a potential security issue, since a hyper-intelligent black hat might find a way to change such data before returning it.
> What if Tapestry stored the associated bytestreams on the server, and provided, in the HTML, just a relatively short pointer (a string id that points to the correct bytestream) to the stream?
> A small amount of additional data on the server side could be used to authenticate the pointer, using the user's session id (if a session exists) and host ip.
> Unreferenced data would be periodically purged.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1797) Mechanism to send pointers to serialized data to the client, not the data itself

Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531816 ] 

Andreas Andreou commented on TAPESTRY-1797:
-------------------------------------------

Have you seen http://www.hdiv.org/ ?

It looks like exactly what you're talking about + I've been wanting to see how it could be integrated into 4 as well

> Mechanism to send pointers to serialized data to the client, not the data itself
> --------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1797
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1797
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>
> Tapestry has the capability to store much data on the client, whether it is persisted page fields, or Form component action data.  This presents a couple of problems; first, it inflates the size of the rendered HTML stream.  Second, it is a potential security issue, since a hyper-intelligent black hat might find a way to change such data before returning it.
> What if Tapestry stored the associated bytestreams on the server, and provided, in the HTML, just a relatively short pointer (a string id that points to the correct bytestream) to the stream?
> A small amount of additional data on the server side could be used to authenticate the pointer, using the user's session id (if a session exists) and host ip.
> Unreferenced data would be periodically purged.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAP5-53) Mechanism to send pointers to serialized data to the client, not the data itself

Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640479#action_12640479 ] 

Massimo Lusetti commented on TAP5-53:
-------------------------------------

How does this relate to the concern of having non-human HTTP clients which act as clients to service exposed by a T5 application as a sort of REST url?

I mean http://service.mycompany.com/ordering/acquire/items.process which is a form form processing special order by vairous point of sales machines widely dislocated.

Now i've solved this issue in the client application hard coding (a sort of hard coding) the t:formdata form parameter. I know this way i'm tightly coupled with that particular version of T5 since if i upgrade the T5 libraries on the server i've to upgrade every single remote client.
How to better deal with that case?

I dream T5 would be able to not use t:formdata at all of have a better support for this particula case.

> Mechanism to send pointers to serialized data to the client, not the data itself
> --------------------------------------------------------------------------------
>
>                 Key: TAP5-53
>                 URL: https://issues.apache.org/jira/browse/TAP5-53
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>
> Tapestry has the capability to store much data on the client, whether it is persisted page fields, or Form component action data.  This presents a couple of problems; first, it inflates the size of the rendered HTML stream.  Second, it is a potential security issue, since a hyper-intelligent black hat might find a way to change such data before returning it.
> What if Tapestry stored the associated bytestreams on the server, and provided, in the HTML, just a relatively short pointer (a string id that points to the correct bytestream) to the stream?
> A small amount of additional data on the server side could be used to authenticate the pointer, using the user's session id (if a session exists) and host ip.
> Unreferenced data would be periodically purged.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAP5-53) Mechanism to send pointers to serialized data to the client, not the data itself

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-53:
-------------------------------------

    Issue Type: New Feature  (was: Bug)

> Mechanism to send pointers to serialized data to the client, not the data itself
> --------------------------------------------------------------------------------
>
>                 Key: TAP5-53
>                 URL: https://issues.apache.org/jira/browse/TAP5-53
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>
> Tapestry has the capability to store much data on the client, whether it is persisted page fields, or Form component action data.  This presents a couple of problems; first, it inflates the size of the rendered HTML stream.  Second, it is a potential security issue, since a hyper-intelligent black hat might find a way to change such data before returning it.
> What if Tapestry stored the associated bytestreams on the server, and provided, in the HTML, just a relatively short pointer (a string id that points to the correct bytestream) to the stream?
> A small amount of additional data on the server side could be used to authenticate the pointer, using the user's session id (if a session exists) and host ip.
> Unreferenced data would be periodically purged.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org