[Glass] large blobs

[Paul DeBruicker]

I don't have any experience with large blobs in GemStone.  

But I did wonder why client requests with the  HTTP Range: header wouldn't
help with your problem.  See

http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html


Presumably the client could/would know exactly how much of the blob data it
already has and then form appropriate requests to just get the missing part
from the filesystem.


Why prefer storing in GemStone vs the Range: scheme?  







johnmci wrote
> I'm collecting thoughts on using gemstone to store large chunks of data
> (say JPGS).  Say 8 to 16MB in size. I have another case of blob data maybe
> upwards of 200MB but I'd store that in chunks just to enable better
> restart
> capabilities when pushing/pulling to a mobile device as that would need to
> restart a previously aborted transmission.
> 
> I'm wondering if anyone has had any experience with this?
> 
> -- 
> ===========================================================================
> John M. McIntosh <

> johnmci@

> >
> Corporate Smalltalk Consulting Ltd. Twitter: squeaker68882
> ===========================================================================
> 
> _______________________________________________
> Glass mailing list

> Glass at .gemtalksystems

> http://lists.gemtalksystems.com/mailman/listinfo/glass





--
View this message in context: http://forum.world.st/Glass-large-blobs-tp4763391p4763403.html
Sent from the GLASS mailing list archive at Nabble.com.