no problem! With some informal testing I found the blobstore absolutely flies along, serves up files as fast as whatever internet connection I tried could handle. I did not load test with multiple users, but I don't doubt this service is built to scale.
The blobstore is meant for file upload and download only. An application cannot usually access data held here directly. There is one exception at present where the GAE image API can access blobstore data files (for example to generate a thumbnail from a large image). But in general using the blobstore will not be suitable for every project. It would be nice to build blobstore API support into a more generic patch to be submitted for inclusion in the web2py source, like for a new blobstore database type. The gae blobstore would be just one possible backend - local db column / file system folder / web service on external url could be others. So on gae and non-gae hosted web2py apps this datatype could be supported. One thing I have yet to figure out with the blobstore API - I'd like to call parseblobinfo(cgi.FieldStorage) in their API directly from web2py code so there is no need to wrap a wgsi call to obtain details about a new blob. But I don't yet know how to build a cgi.FieldStorage object from the regular web2py webpage request. - Alex On Feb 23, 11:25 pm, villas <[email protected]> wrote: > Wow, you only heard of blobstore yesterday --that's quick! > If you start using it more, perhaps you would comment on the speed. > I imagine that some people might want to just store everything in > there, big and small files, just for the convenience of having them > all in one place. > Thanks for the slice! > D -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
