carllerche

16 ms·

121.
by carllerche 11y ago
Replying here since I can't reply to your deeper comment. A client can never know with certainty that it has successfully acquired the lock because, for example, the process could freeze between reading the current time from hardware
122.
by carllerche 11y ago
References to what specifically? Martin provided a number in his original blog post, I also elaborated a bit more on my various points in other comments.
123.
by carllerche 11y ago
In short, either the storage layer provides enough guarantees to ensure safety without redlock OR it is not possible to ensure safety. I believe that antirez's proposal is the former, but if he has a safe algorithm that does not requ
124.
by carllerche 11y ago
What if the system freezes between reading the current time from the hardware and the stead_time function returning? In short, you CANNOT rely on time in any way shape or form for safety . You can only use it as advice & to get livel
125.
by carllerche 11y ago
Martin made no mention of strong vs. eventual consistency. If you write to a store like cassandra using a monotonic token, the result will converge correctly. If you require to never read "stale" data, you can read / write w&
126.
by carllerche 11y ago
I don't need to, Martin did an excellent job touching on this in his original post, including real world references.
127.
by carllerche 11y ago
This response is incorrect at a very fundamental level. First, Antirez claims that requiring the "materialization" store to be able to tie break with a monotonically increasing token requires linearization? This is completely fals
128.
by carllerche 11y ago
Looks good. The post did not mention HA (that I saw), which caused the confusion.
129.
by carllerche 11y ago
Looks interesting. There is definitely a need for something secure to manage secrets easily & efficiently. I'm not super familiar with Shamir's secret sharing. The post says that the master key is split up across a number of p
130.
by carllerche 11y ago
Here is how we bind the Skylight gem to the Rust bit: https://github.com/skylightio/skylight-ruby/blob/master/ext/...
131.
by carllerche 11y ago
`thread::scoped` attempts to use lifetimes in order to enforce that values on the parent thread's stack would live throughout the life of the child thread, such that it would be safe to pass references to values on the parent thread to
132.
by carllerche 12y ago
Well, Rust doesn't have any opinions regarding blocking or not. Currently, std::io implements blocking IO, but as you pointed out, Rust allows libraries to implement non-blocking / async paradigms.
133.
by carllerche 12y ago
Rust has definitely been a pleasure to work with. I have been experimenting with a Future & Stream [1] abstraction in Rust that would allow easily describing complex concurrent and async operations and to allow easy composition, not unl
134.
by carllerche 12y ago
Well, http://github.com/carllerche/curl-rust has been working great for me. Sure, it uses libcurl so it isn't pure Rust, but that doesn't make it not work :-)
135.
by carllerche 12y ago
This would only be possible on very new linux kernels (that provide user namespacing)
136.
by carllerche 12y ago
Rust uses LLVM for all code generation and optimization. So, in that respect, it is very mature and I personally have never hit an issue.
137.
by carllerche 12y ago
Actually, Rust is much closer to the system than Go is making it possible to implement lighter weight web services using Rust than Go. Rust features like not having a GC allows for much more predictable performance. Go's concurrency fe
138.
by carllerche 13y ago
a) no to cargo exec b) If you have a better solution for bundler, please open an issue and suggest it. c) There are few simple solutions to avoid `bundle exec`, which is mostly there to make things easier when getting started. I'm sure
139.
by carllerche 14y ago
Ordinary users would do it because many corporate sites used to direct them to do this as a fix for their browsers displaying invalid characters.
140.
by carllerche 15y ago
Instead of memoizing in the server you could memoize in the browser and use socket.io to ask connected browsers if they have a memoized value for a given fib number. That would get you around the limitations that bascule mentioned.
141.
by carllerche 15y ago
I don't think I would consider package dependencies to be magic. Also, the solution to this whole problem is simply `bundle install --binstubs && bin/rake test`. I don't really think there is much to freak out about.
142.
by carllerche 16y ago
Have you ever actually taken part of an online discussion?