buckit

gsadmin/buckit

Fork 0

mirror of https://github.com/buckit-io/buckit.git synced 2026-09-20 17:43:26 +00:00

Commit Graph

Author	SHA1	Message	Date
Krishna Srinivas	01cbacd803	object-cache: use golang bytes.Buffer and bytes.NewReader instead of custom implementation. (#2108 )	2016-07-06 01:29:49 -07:00
Harshavardhana	8a028a9efb	handler/PUT: Handle signature verification through a custom reader. (#2066 ) Change brings in a new signVerifyReader which provides a io.Reader compatible reader, additionally implements Verify() function. Verify() function validates the signature present in the incoming request. This approach is choosen to avoid complexities involved in using io.Pipe(). Thanks to Krishna for his inputs on this. Fixes #2058 Fixes #2054 Fixes #2087	2016-07-05 01:04:50 -07:00
Harshavardhana	d2557bb538	XL: GetObject caching implemented for XL. (#2017 ) The object cache implementation is XL cache, which defaults to 8GB worth of read cache. Currently GetObject() transparently writes to this cache upon first client read and then subsequently serves reads from the same cache. Currently expiration is not implemented.	2016-07-03 17:15:38 -07:00

Author

SHA1

Message

Date

Krishna Srinivas

01cbacd803

object-cache: use golang bytes.Buffer and bytes.NewReader instead of custom implementation. (#2108 )

2016-07-06 01:29:49 -07:00

Harshavardhana

8a028a9efb

handler/PUT: Handle signature verification through a custom reader. (#2066 )

Change brings in a new signVerifyReader which provides a io.Reader
compatible reader, additionally implements Verify() function.

Verify() function validates the signature present in the incoming
request. This approach is choosen to avoid complexities involved
in using io.Pipe().

Thanks to Krishna for his inputs on this.

Fixes #2058
Fixes #2054
Fixes #2087

2016-07-05 01:04:50 -07:00

Harshavardhana

d2557bb538

XL: GetObject caching implemented for XL. (#2017 )

The object cache implementation is XL cache, which defaults
to 8GB worth of read cache. Currently GetObject() transparently
writes to this cache upon first client read and then subsequently
serves reads from the same cache.

Currently expiration is not implemented.

2016-07-03 17:15:38 -07:00

3 Commits