felixge

19 ms·

151.
by felixge 13y ago
Would the down-voters care to explain? I've pointed out how another platform deals with allocating raw memory buffers as it's relevant to the discussion. I've made no claims of it being superior, and in fact, am largely using
152.
by felixge 13y ago
FWIW: Node.js uses a buffer cache like this by default: https://github.com/joyent/node/blob/master/lib/buffer.js
153.
by felixge 13y ago
License is Apache 2: https://github.com/google/gumbo-parser/blob/master/COPYING
154.
Vim Trick: Open current line on GitHub(felixge.de)
3 points by felixge 13y ago|0 comments
155.
by felixge 13y ago
I'd also love to see support for draining - and it seems like we might be in luck in the near future: https://forums.aws.amazon.com/thread.jspa?threadID=61278&sta... ^-- BenF@AWS commented on June 10th saying that
156.
by felixge 14y ago
So far we have this: > Servers MUST handle overlapping PUT requests in an idempotent fashion given that the overlapping data is identical. Otherwise the behavior is undefined. Does that adress your concern?
157.
by felixge 14y ago
: ) - hopefully that's not the case here, afaik our protocol is the first proposal in this space meant for general adoption. All prior art is tied to specific libraries and services.
158.
by felixge 14y ago
Depending on the use case, man in the middle attacks could be a good reason for hashing.
159.
by felixge 14y ago
I love S3, and we use it all over the place at transloadit. I realized my comment sounded overly negative, so I added a clarification to my comment: Our goal is to bring resumable file uploads to the entire planet, S3 or any other proprieta
160.
by felixge 14y ago
> But the Range header surely can't be used here, since it's a request header and this is a response. We're currently discussing how to interpret RFC 2616 (http 1.1) for this here: https://github.com/tus/tus-resumable-upload-protocol/i
161.
by felixge 14y ago
I don't consider professionalism and the word "fuck" to be mutually exclusive, but at the end of the day we'll focus on what attracts people. Our current choice of words clearly fails at this goal, so we'll consider replacing it.
162.
by felixge 14y ago
Your library looks great - thanks for releasing it! S3 is an incredible offering, but since I'm working on tus.io, I'll focus on what's wrong with it : ) - Multipart chunks need to be 5 MB at least. An interrupted part cannot be resumed. Th
163.
by felixge 14y ago
Node.js was a good choice for Transloadit when we started (2009). By good I mean better than PHP which we tried using for transloadit before. I started playing with Go late last year, so far I'm under the impression that it's easier to writ
164.
by felixge 14y ago
> Is it possible that the data that is already there could be corrupt? TCP error correction should take care of this for most parts, but we're actively discussing adding support for stronger guarantees: https://github.com/tus/tus-resum
165.
by felixge 14y ago
Point taken. We'll try to hit a better balance between emotionalizing the subject without being too exclusive when iterating the text for this again. https://github.com/tus/tus.io/issues/14
166.
by felixge 14y ago
The urls don't have to be fixed. I'll clarify this in the docs: https://github.com/tus/tus-resumable-upload-protocol/issues/... Also: The protocol is still under heavy development, so please post any additional ideas, issues, patches or f
167.
by felixge 14y ago
Thanks for the kind words! Tus.io the beginning of a larger commitment to open source here at Transloadit, which will also translate into many new features (resumable uploads being the next one).
168.
A protocol for resumable file uploads(tus.io)
2 points by felixge 14y ago|0 comments
169.
The Nodecopter Cloud Store(tus.io)
1 points by felixge 14y ago|0 comments
170.
Let's Fix File Uploading(felixge.de)
5 points by felixge 14y ago|0 comments
171.
by felixge 14y ago
Will there be drones playing forkmaster? http://forkmaster.com/
172.
by felixge 14y ago
I realize it's very far away, but there is going to be an event in Sydney. Ping me at felix@nodecopter.com if you'd like me to connect you with the organizer!
173.
by felixge 14y ago
Awesome! We'll also help to connect people if there are applications for the same city!
174.
The Summer of Drones(summerofdrones.com)
50 points by felixge 14y ago|14 comments
175.
The Pull Request Hack(felixge.de)
198 points by felixge 14y ago|34 comments
176.
by felixge 14y ago
> What I take from the whole article is the author severely underestimates the true cost of software. I was talking about the "costs of ownership", not the "costs of development". And I'd like to think I understand both.
177.
by felixge 14y ago
+100 to this. Whenever I get a bug report, I check the users Github profile. I spend much more time helping people who are also contributing (to any project, not just mine) than those with no apparent track record.
178.
by felixge 14y ago
> I think that captures the spirit of open source much better: legally we have no responsibility, but we're still going to try to make it useful. Fully agreed. And I actually think that was TJ's intention when he decided to merge a pull
179.
Open Source And Responsibility(felixge.de)
54 points by felixge 14y ago|25 comments
180.
by felixge 14y ago
Go supports panic/recover which is very similar to exceptions. Instead of wrapping a try...catch block around something, you get to handle exceptions every time they are about to cause a function to be exited. This means you can't continue

More ›