Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

read from buffer #21

Open
tj opened this issue Sep 17, 2013 · 13 comments · May be fixed by #50
Open

read from buffer #21

tj opened this issue Sep 17, 2013 · 13 comments · May be fixed by #50

Comments

@tj
Copy link

tj commented Sep 17, 2013

would you be interested in a patch for reading from a buffer? in our case we have the blob in memory already so less IO would be nice

@dberesford
Copy link
Owner

Hi TJ - sounds interesting, and yes, definitely interested!

@drewish
Copy link
Collaborator

drewish commented Mar 8, 2015

Looks like someone did a fork to handle that usecase: https://www.npmjs.com/package/exiv2-buffers

@rayshan
Copy link

rayshan commented Jul 29, 2015

+1 would you be interested to merge fork's changes back into master? Would help when used as a gulp plugin.

cc @bertrandom

@dberesford
Copy link
Owner

@rayshan yes interested of course - pull requests very welcome!

@bertrandom
Copy link

Hi! I made the fork, I'll try to make a PR when I have a moment free.

@JDOSR
Copy link

JDOSR commented Jun 17, 2016

I've add issues trying to install the exiv2-buffers package, has anyone been able to install the node dependency? The original package works fine, this package, much like the gem, breaks on accessing the exiv2/image.hpp

CXX(target) Release/obj.target/exiv2/exiv2node.o
../exiv2node.cc:9:10: fatal error: 'exiv2/image.hpp' file not found
#include <exiv2/image.hpp>
^
1 error generated.
make: *** [Release/obj.target/exiv2/exiv2node.o] Error 1

Anyone have success with this?

@atwright147
Copy link

@bertrandom (or anybody else) would you be willing to get your code updated to be compatible with the current state of exiv2node?

I could really use the updated functionality but I don't know enough about how this works or C to be able to do it myself

valpackett added a commit to valpackett/exiv2node that referenced this issue Jun 5, 2017
seems like writing to a buffer does not save though, for now only
reading works
@valpackett valpackett linked a pull request Jun 5, 2017 that will close this issue
@valpackett
Copy link

@atwright147 I've implemented buffer support, but only reading tags/previews works for now, not writing/deleting (looks like the buffer gets copied somewhere in the V8 API and the updated buffer doesn't get into JS land)

@atwright147
Copy link

@myfreeweb Awesome! I'll try this out when I get chance :)

@atwright147
Copy link

@myfreeweb Would you please see if your fork fixes this issue?: #49

@valpackett
Copy link

@atwright147 yep my fork gets two correct tiff images

@atwright147
Copy link

@myfreeweb could you enable issues for that repo please? I have one to report :)

@valpackett
Copy link

@atwright147 sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants