Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Custom resolver system outside of taglib #28

nikhilm opened this Issue May 23, 2012 · 0 comments


None yet
1 participant

nikhilm commented May 23, 2012

The current mutex based system works, but it has one significant taglib level shortcoming that FileTypeResolver takes only filenames and not IOStream.

In addition, the requirement that no v8 activity occurs in a worker thread requires hacks like the mutex one currently in place. This is obviously not fun, and at some point I want to allow resolvers themselves to notify the format via a callback. Finally reading and writing from buffers using BufferStream means that JS resolvers should be able to get a buffer as an argument.

So we need our own system, that will trigger the callbacks sequentially whenever a read is attempted, then use the format string to create the right File wrapping the BufferStream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment