[Seaside] Strategies for bulky renders/updates
milan.mimica at gmail.com
Sun Mar 13 18:09:08 UTC 2011
radoslav hodnicak wrote:
> Well I don't plan to use database IDs on the page directly - for one
> they are like 20+ characters long (UUIDs), so that would defeat some
> of the reasons for doing this (less data sent over the wire), and yes
> it's a security hole. I'm just going to have an element id <-> object
> mapping on the server, which isn't really different from having
> callback IDs embedded in the html.
The ID's are persistent, unlike Seaside callback urls. I think that's even more
important. One could reuse ID (encripted or not) later to access objects. I'm
just thinking about my aplication. It may not be an issue to some.
More information about the seaside