Robert Carlsen

Hm - probably not worth the trouble then. You could rewrite taglib in go :P On Fri, Apr 10, 2015 at 11:56 AM, Trevor [email protected] wrote: > I agree, but...

Shifting to streaming under the hood will make it difficult to continue to support ``file.Seek`` and ``file.WriteAt``. The only alternatives I can think of are to either have those methods...

I'd like to contribute to making some progress on this but would like a bit of guidance before moving forward. Making client.Put take a reader instead of a byte slice...

Browsing through the codebase, it looks like although streaming reads are supported, the capability is not really used. ``upspinfs``, for example, seems to read and cache the entire file whenever...

Currently, ``file.File`` operates directly through the client API. It will either need to stop doing that and start interacting more directly with the dir/store servers or the client API will...

I'm finding that several unexported methods and functions in the client package will need to be mostly reimplemented in the client/file package to get this to work (e.g. client.lookup, client.addReaders,...

clientutil looks like an okay option. I've run into a hiccup: In order to put things in clientutil, the ``File`` object needs access to the ``upspin.Config`` object for the client...

My time to work on this is somewhat intermittent. I hope to have something within a week or two. If anybody else wants to work on it feel free to...

I'm not convinced (yet) that a straight up singleton is the best approach, but I'm definitely not a huge fan of the status quo. I actually don't mind passing in...

This should be pretty straight forward. We'll need to add something similar to `Harness.update_config` that allows tests to set what the action params/args are when the event is triggered -...