Queues browser files and uploads them in chunks through Topic: On normal completion, the worker adds a When the request has a response topic, it receives the initial queue request\nobject. This acknowledgement does not mean that uploading has finished. Use the\nconfigured completion and failure topics for the result. An empty file array\ndoes not create an upload request; a call instead receives the immediate error\npayload The worker initializes files through\n Topic: Delete the upload identified by its server upload name. The worker removes its\nlocal upload state and requests deletion through the server model. The payload\nis ignored and the command does not reply.<\/p>\n Topic: Internal scheduling trigger used when a block finishes. Applications should\nsubmit files through mod_fileuploader<\/code>.\nThe _fileuploader_worker.tpl<\/code> include starts the worker. It depends on\nbridge\/origin<\/code> and advertises the capability fileuploader<\/code> (without model\/<\/code>).<\/p>\npost\/new<\/h2>\n
model\/fileuploader\/post\/new<\/code>.<\/p>\nPayload field<\/th> Meaning<\/th><\/tr><\/thead> files<\/code><\/td>Non-empty array of { name, file, upload }<\/code> objects. file<\/code> is a browser File<\/code>; name<\/code> identifies the form field; upload<\/code> optionally supplies the server upload name.<\/td><\/tr>ready_topic<\/code>, ready_msg<\/code><\/td>Destination and base payload for completion.<\/td><\/tr> failure_topic<\/code>, failure_msg<\/code><\/td>Destination and payload for failure.<\/td><\/tr> progress_topic<\/code>, progress_msg<\/code><\/td>Destination and base payload for progress updates.<\/td><\/tr> start_topic<\/code><\/td>Optional destination for each file's upload state after server initialization.<\/td><\/tr><\/tbody><\/table>\n cotonic.broker.publish("model\/fileuploader\/post\/new", {\n files: [{ name: "document", file: fileInput.files[0] }],\n ready_topic: "my\/upload\/ready",\n ready_msg: {},\n failure_topic: "my\/upload\/failed",\n failure_msg: {},\n progress_topic: "my\/upload\/progress",\n progress_msg: {}\n});\n<\/code><\/pre>\nfileuploader<\/code> array to ready_msg<\/code>.\nEach entry is { name, upload }<\/code>, where upload<\/code> is the server upload identifier.\nFor a Zotonic postback_event<\/code>, it instead appends fileuploader references to the\npostback's query arguments. Progress payloads add percentage<\/code>; failure publishes\nthe supplied failure payload.<\/p>\n{ status: "error", error: "No files" }<\/code> on its response topic.<\/p>\nbridge\/origin\/model\/fileuploader\/post\/new<\/code>, then sends blocks to the returned\nHTTP upload URL. This browser model and the server fileuploader model have\ndifferent payload contracts.<\/p>\npost\/delete\/+name<\/h2>\n
model\/fileuploader\/post\/delete\/+name<\/code>.<\/p>\npost\/next<\/h2>\n
model\/fileuploader\/post\/next<\/code>.<\/p>\npost\/new<\/code> rather than manage this scheduling topic.<\/p>\n