Copy, Cut and Cookies: a CopySupport.py question
To someone with perhaps more ZZen than myself .... I am trying to understand CopySupport.py - It seems that objects that are cut or copied are stored in a cookie on the client. I could see how this would be easier than trying to associate some stored data item on the server with a particular client browser, but it also seems somewhat inefficient (esp. as regards upload and download times from the client) unless the object is relatively small in size and I also wonder if this scheme would break down completely for a big object, say something a few MB in size. Am I missing something ? Or maybe this is the only reasonably sane way to do it. TIA Jeff Sasmor jeff@sasmor.com www.netkook.com is an "open Zope CMF site"
Jeff Sasmor wrote:
To someone with perhaps more ZZen than myself ....
I am trying to understand CopySupport.py -
It seems that objects that are cut or copied are stored in a cookie on the client.
Not the objects, but the path to the objects are stored in a cookie. To be more precise, Zope takes the list of object paths the user has chosen and compresses and encodes in in ASCII.
I could see how this would be easier than trying to associate some stored data item on the server with a particular client browser, but it also seems somewhat inefficient (esp. as regards upload and download times from the client) unless the object is relatively small in size and I also wonder if this scheme would break down completely for a big object, say something a few MB in size.
The cookie is between about 100 bytes and 4K (if you select a lot of objects). Shane
participants (2)
-
Jeff Sasmor -
Shane Hathaway