I get to the point of uploading image and viewing it. I am referencing image by its key value. The problem arise when user need to change the image. There are two alternate way to do that.
First is to retrieve the previous image data. and overwrite with the new one. so as the key of the original image remain intact. but as i am serving image which are highly cached ,there is very unlikely for the user to actually see the changed image. Second idea is to delete the previous image, Insert the new image. But as due to some reason , inserts are really slow, even if I got the key of the image , image is not actually available. i.e. the latency problem. So my question is , How to solve this latency problem ? Another question is , is it good to store image detail inside separate image entity or in the "userinfo" entity ? I am also worrying about garbage collections -- i.e. images that are stored in datastore but are not being referred by anyone. how you guys handling this issue ? Thanks & Regards, Gopal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---