Why is this not a URL? We do exactly the same thing, except for flash movies generated from powerpoint. The URL we use is actually an S3 url (Amazon S3). <br>The only issue which you might want to consider is things like replication and garbage collection for these large objects - in some cases you would need to build your own. In our case, its simple, these objects are not shared, and S3 provides the redundancy.
<br>Of course, instead of something like S3 you could use a decent file system (ZFS in solaris is nice). Other alternatives are mogileFS, nutch file system -- if you want a replicated file system with simple semantics. Of course I would argue that mogileFS is better off rewritten in erlang -- but thats a project for another day.
<br><br>Vijay<br><br><br><div><span class="gmail_quote">On 5/10/07, <b class="gmail_sendername">Joe Armstrong</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'd like to store large objects in a persistent disk store.<br><br>Dets is "almost" ok.<br><br>Dets is a key-value store - but there will be problems if the value is<br>large (think a 4 Gbyte movie)<br><br>What I need is an interface that allows random access of large values
<br><br> dets:reserve_space_for_key(LargeKey, 2000000000) reserve 2 GB<br> dets:store(LargeKey, Start, <<bin>>)<br> dets:lookup(largeKey, Start, Len) -> <<bin>><br><br>Now I know that dets does not do this now.
<br><br>Now the questions<br><br> - to those of you who have hacked dets - is this an easy extension to dets?<br> - should I hack dets?<br> - should I "roll-my-own"<br> - has anybody already made a large object disk storage thingy
<br><br>/Joe<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:firstname.lastname@example.org">email@example.com</a><br><a href="http://www.erlang.org/mailman/listinfo/erlang-questions">