random-access-storage / random-access-http Goto Github PK

Hello. We've started a group to bring more attention to random access implementations. @mafintosh has just completed the latest abstract class for implementors with 100% test coverage. Please consider joining the group and relocating your repo to:

https://github.com/random-access-storage

You should receive your invite shortly. Thanks!

@e-e-e @bcomnes may I?

Also do you guys have the rights to publish on npm?

I am opening this issue to discuss merging our two implementations.

I have not moved https://github.com/e-e-e/http-random-access into the random-access-storage org yet as I knew that this module already existed and it felt silly to have two versions of essentially the same thing. However they are structurally different.

I created http-random-access for use as a drop in replacement for raf and ram in dat storage. random-access-http does not work for this purpose as it requires absolute urls, and throws errors on write. http-random-access also uses axios rather than nodes native http module, so that its browser compatible.

I just updated my implementation to use the latest random-access-storage and while I was at it I made it work with absolute urls too in addition to relative urls. It now also passes your tests in addition to mine. I wanted to suggest that we simply merge my implementation into this repository and do a major version bump, and deprecate http-random-access. Although is there anything in this implementation that is not currently covered by http-random-access? Have I missed anything?

What are your thoughts @bcomnes, @mafintosh, @scriptjs, @juliangruber?

Here is an uncooperative static file server:

https://www.npmjs.com/package/st#range-requests

See: https://www.npmjs.com/advisories/880

Version 1.0.3 of pump was just published.

This version is covered by your current version range and after updating it in your project the build failed.

pump is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Assume http?

Right now you need to provide a {http,https}:// prefixed url.