Date | Commit message (Collapse) |
|
It's more future-proof, this way.
|
|
100% RDoc coverage (not that it's an indicator of _good_
documentation, but we're getting there)
|
|
This should make documentation easier
|
|
Putting this into the MogileFS::Put::* namespace will
make it easier to document.
|
|
This returns a new HTTPStream object that behaves
like a writable IO object with the following methods:
* write
* print
* printf
* putc
* puts
* syswrite
* <<
..and also responds to IO.select (for writability)
|
|
* re-document exception classes
* latest upstream MogileFS is 2.55
|
|
In case somebody wants to use this to override the
default class for copy_stream in Ruby. It's also
easier to read, this way.
|
|
PipelineError was misnamed should be recoverable in user code.
MogileFS::Error should be raised for bugs (in our code or
user's code).
|
|
* origin/pipeline:
list_keys/each_key: better handling of verbose listings
pipeline: make errors easier to debug by including the request
initial pipeline API
|
|
GIT-VERSION-GEN was ported from Bourne shell to Ruby.
|
|
This is useful for the "verbose" listing of keys since
we make a lot of file_info calls here. This API feels
very awkward, but I think it's unavoidable...
|
|
|
|
Trying to find a happy medium within Hoe while keeping
my preference for gmake and forcing wrongdoc on readers:
JavaScript and GUIs all suck :P
|
|
Each backend could have a different story to tell
|
|
Ruby 1.9.3 considers them harmful
|
|
Avoid deepening stack depth and make it easier to migrate
fully to 1.9 in the future (dropping 1.8 support).
|
|
|
|
Should be easier to read this way
|
|
= 2.2.0
* internal cleanups (no public API breakage)
* refactor backend socket/connection handling for reliability
There'll probably be more aggressive cleanups/refactoring in
future releases if I have time.
|
|
The 3.x.x series will probably be incompatible with 2.x.x...
|
|
We won't trust Ruby 1.9 String weirdness since data storage
is locale-agnostic
|
|
|
|
|
|
|
|
MogileFS 2.x upstream no longer supports it, and it's
become a maintenance burden and NFS is a horrible thing
anyways.
Attempting to use this with servers that support NFS will result
in MogileFS::UnsupportedPathError being raised.
|
|
This removes the dependency on unsafe methods used in the
Timeout class.
Charles makes some good points here:
http://blog.headius.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html
And even matz agrees:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/294446
Of course, I strongly dislike any unnecessary use of threads,
and implementations using native threads to do timeouts makes me
even more uncomfortable.
|
|
Needs more tests, but it seems to work...
I seem to have discovered a bug in mogtool which causes it to
generate incorrect MD5 checksums when the --gzip flag is used
(and --gzip actually just does zlib deflate, not something that
gzip(1) can actually decrypt).
So right now MD5 checksums are only verified on non-zlib-deflated
files.
|
|
|
|
The ArgumentErrors happen at initialization time, so
I'll keep those as-is
|
|
|
|
Also easier to trap and deal with
|
|
This will allow users to trap MogileFS::Error to trap errors
specific to our library.
|
|
|
|
|
|
From p4 revision #3336
git-svn-id: http://seattlerb.rubyforge.org/svn/mogilefs-client/dev@376 d2e05cf2-00e0-46e5-a3de-bbee4d6b9404
|