go-exif

Author	SHA1	Message	Date
Dustin Oprea	0e3dba6a88	modules: Cleanup	2022-10-03 10:15:34 -04:00
Dustin Oprea	517e30a4d3	go.mod: Update to latest	2022-10-03 10:11:15 -04:00
Dustin Oprea	9393e7afd4	Upgrade from go-utility v1 to v2	2020-07-17 03:10:58 -04:00
Dustin Oprea	f93c06e0d6	v3: Fix import naming glitch	2020-07-16 21:33:45 -04:00
Dustin Oprea	208788de28	go.mod: Drop go-utility replacement and update sums	2020-07-11 14:06:20 -04:00
Dustin Oprea	312218d7b1	Use encapsulated data/reader rather than bytes Given a stream of data, it is possible to determine the beginning of EXIF data but not the end. Therefore, either an image-aware implementation must know how to parse an image and extract the EXIF data or a brute-force search implementation (one of which is provided by this project) must find the start anchor and then return all bytes from that to the end of the file. We have been made aware of some use-cases where a brute-force search might be unavoidable due to trust or stability issues with the image structure. This leads to large allocations. This can be avoided by accomodating support that will allow for both a byte-slice or an `io.ReadSeeker`. Since the EXIF structure is typically not read- intensive (a couple of kilobytes if no thumbnail is present), this should have a minimal performance impact. Closes #42	2020-07-11 12:12:48 -04:00
Dustin Oprea	56058635d0	Seed v3 release. Copy from v2 release.	2020-07-11 12:12:48 -04:00