Hi, a couple of points from my side
a) The 1 Mb limit of Datastore can be overcome: you can make collections of blobs object in a class and read one 1 after the other in order to serve them. b) The blobstore was until 1.4 much more painful to update: uploads were from the client etc. So, before 1.4, I was trying to avoid blobstore as much as possible. c) Anyway, even if blobstore has now a File interface since 1.4 which makes updates simpler, I would still favor blobstore because you serve your html via a regular servlet on which you can apply all the OO techniques that you need (inheritance, dependency injection, etc...) . On blobstore, you get alerted after file was served so you can't be as smart and efficient d) Also, reporting on the console for the blobstore is less precise than for servlets So, I would still go the ds way as much as possible ! (You can also mix the 2 approaches) regards didier On May 5, 6:34 pm, bradr <[email protected]> wrote: > I have an app that stores XML and HTML files, and i'm trying to decide > on the Blobstore vs. Datastore > > Pro for Blobstore: it is possible for the HTML files to exceed 1 MB > (although I have ready the average size of an HTML file is ~25 KB) > > Pro for Datastore: The blobstore allows for insert / deletes only, no > updates. So I would have to delete blobs and insert new blobs every > time a user saves an existing file, which could happen a few time a > minute (similar to editing a file in Google docs) > > From a technical perspective, are there any repercussions to: > a) serving HTML files from the datastore vs. > b) serving HTML files fro the blobstore, but constantly having to add > and delete blobs? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
