An attachment is a simple write-once entity that allows, potentially large, arbitrary content to be stored in related to any proper entity. Attachments mirror the behavior of e-mail attachments; they can be created, retrieved, and deleted. The contents of an Attachment can never be modified; this avoids any concerns with versioning or conflict resolution.
Attachments can be created and retrieved by HTTP using the [AttachFS] REST protocol.
The attachment entity is improper. It is identified by an automatically assigned GUID value and does not have an object id.
An attachment has identical access to the Attachment entity that it has to the related entity and the creator (owner) of the attachment always has complete access.
Complete access to an Attachment is "aiwmdrf"; this considered access is excessive as "a" (Administrative) privileges have no meaning as ACLs/ACEs cannot be assigned to attachments , "m" (Modicication) has no meaning as attachment content cannot be modified, and no "f" (Form) support is implemented for Attachments. It is in order to facilitate any type of site-specific application that may be aware of permissions flags that these attributes are included in the access evaluation.
Name | Type | Description |
---|---|---|
uuid | String(255) / GUID | |
related_id | Integer | |
kind | String(45) | |
mimetype | String(128) | |
created | Integer | |
size | Integer | |
expiration | Integer | |
context_id | Integer | |
webdav_uid | String(128) | |
checksum | String(128) |