141 lines
6.4 KiB
Go
141 lines
6.4 KiB
Go
package handler
|
|
|
|
import (
|
|
"context"
|
|
"io"
|
|
)
|
|
|
|
type MetaData map[string]string
|
|
|
|
type FileInfo struct {
|
|
ID string
|
|
// Total file size in bytes specified in the NewUpload call
|
|
Size int64
|
|
// Indicates whether the total file size is deferred until later
|
|
SizeIsDeferred bool
|
|
// Offset in bytes (zero-based)
|
|
Offset int64
|
|
MetaData MetaData
|
|
// Indicates that this is a partial upload which will later be used to form
|
|
// a final upload by concatenation. Partial uploads should not be processed
|
|
// when they are finished since they are only incomplete chunks of files.
|
|
IsPartial bool
|
|
// Indicates that this is a final upload
|
|
IsFinal bool
|
|
// If the upload is a final one (see IsFinal) this will be a non-empty
|
|
// ordered slice containing the ids of the uploads of which the final upload
|
|
// will consist after concatenation.
|
|
PartialUploads []string
|
|
|
|
// stopUpload is the cancel function for the upload's context.Context. When
|
|
// invoked it will interrupt the writes to DataStore#WriteChunk.
|
|
stopUpload context.CancelFunc
|
|
}
|
|
|
|
// StopUpload interrupts an running upload from the server-side. This means that
|
|
// the current request body is closed, so that the data store does not get any
|
|
// more data. Furthermore, a response is sent to notify the client of the
|
|
// interrupting and the upload is terminated (if supported by the data store),
|
|
// so the upload cannot be resumed anymore.
|
|
func (f FileInfo) StopUpload() {
|
|
if f.stopUpload != nil {
|
|
f.stopUpload()
|
|
}
|
|
}
|
|
|
|
type DataStore interface {
|
|
// Create a new upload using the size as the file's length. The method must
|
|
// return an unique id which is used to identify the upload. If no backend
|
|
// (e.g. Riak) specifes the id you may want to use the uid package to
|
|
// generate one. The properties Size and MetaData will be filled.
|
|
NewUpload(info FileInfo) (id string, err error)
|
|
// Write the chunk read from src into the file specified by the id at the
|
|
// given offset. The handler will take care of validating the offset and
|
|
// limiting the size of the src to not overflow the file's size. It may
|
|
// return an os.ErrNotExist which will be interpreted as a 404 Not Found.
|
|
// It will also lock resources while they are written to ensure only one
|
|
// write happens per time.
|
|
// The function call must return the number of bytes written.
|
|
WriteChunk(id string, offset int64, src io.Reader) (int64, error)
|
|
// Read the fileinformation used to validate the offset and respond to HEAD
|
|
// requests. It may return an os.ErrNotExist which will be interpreted as a
|
|
// 404 Not Found.
|
|
GetInfo(id string) (FileInfo, error)
|
|
}
|
|
|
|
// TerminaterDataStore is the interface which must be implemented by DataStores
|
|
// if they want to receive DELETE requests using the Handler. If this interface
|
|
// is not implemented, no request handler for this method is attached.
|
|
type TerminaterDataStore interface {
|
|
// Terminate an upload so any further requests to the resource, both reading
|
|
// and writing, must return os.ErrNotExist or similar.
|
|
Terminate(id string) error
|
|
}
|
|
|
|
// FinisherDataStore is the interface which can be implemented by DataStores
|
|
// which need to do additional operations once an entire upload has been
|
|
// completed. These tasks may include but are not limited to freeing unused
|
|
// resources or notifying other services. For example, S3Store uses this
|
|
// interface for removing a temporary object.
|
|
type FinisherDataStore interface {
|
|
// FinishUpload executes additional operations for the finished upload which
|
|
// is specified by its ID.
|
|
FinishUpload(id string) error
|
|
}
|
|
|
|
// LockerDataStore is the interface required for custom lock persisting mechanisms.
|
|
// Common ways to store this information is in memory, on disk or using an
|
|
// external service, such as ZooKeeper.
|
|
// When multiple processes are attempting to access an upload, whether it be
|
|
// by reading or writing, a synchronization mechanism is required to prevent
|
|
// data corruption, especially to ensure correct offset values and the proper
|
|
// order of chunks inside a single upload.
|
|
type LockerDataStore interface {
|
|
// LockUpload attempts to obtain an exclusive lock for the upload specified
|
|
// by its id.
|
|
// If this operation fails because the resource is already locked, the
|
|
// tusd.ErrFileLocked must be returned. If no error is returned, the attempt
|
|
// is consider to be successful and the upload to be locked until UnlockUpload
|
|
// is invoked for the same upload.
|
|
LockUpload(id string) error
|
|
// UnlockUpload releases an existing lock for the given upload.
|
|
UnlockUpload(id string) error
|
|
}
|
|
|
|
// GetReaderDataStore is the interface which must be implemented if handler should
|
|
// expose and support the GET route. It will allow clients to download the
|
|
// content of an upload regardless whether it's finished or not.
|
|
// Please, be aware that this feature is not part of the official tus
|
|
// specification. Instead it's a custom mechanism by tusd.
|
|
type GetReaderDataStore interface {
|
|
// GetReader returns a reader which allows iterating of the content of an
|
|
// upload specified by its ID. It should attempt to provide a reader even if
|
|
// the upload has not been finished yet but it's not required.
|
|
// If the returned reader also implements the io.Closer interface, the
|
|
// Close() method will be invoked once everything has been read.
|
|
// If the given upload could not be found, the error tusd.ErrNotFound should
|
|
// be returned.
|
|
GetReader(id string) (io.Reader, error)
|
|
}
|
|
|
|
// ConcaterDataStore is the interface required to be implemented if the
|
|
// Concatenation extension should be enabled. Only in this case, the handler
|
|
// will parse and respect the Upload-Concat header.
|
|
type ConcaterDataStore interface {
|
|
// ConcatUploads concatenations the content from the provided partial uploads
|
|
// and write the result in the destination upload which is specified by its
|
|
// ID. The caller (usually the handler) must and will ensure that this
|
|
// destination upload has been created before with enough space to hold all
|
|
// partial uploads. The order, in which the partial uploads are supplied,
|
|
// must be respected during concatenation.
|
|
ConcatUploads(destination string, partialUploads []string) error
|
|
}
|
|
|
|
// LengthDeferrerDataStore is the interface that must be implemented if the
|
|
// creation-defer-length extension should be enabled. The extension enables a
|
|
// client to upload files when their total size is not yet known. Instead, the
|
|
// client must send the total size as soon as it becomes known.
|
|
type LengthDeferrerDataStore interface {
|
|
DeclareLength(id string, length int64) error
|
|
}
|