#529: Changes to Video Upload & Publish Form
-------------------------------+--------------------------------------------
Reporter: anna | Owner:
Type: task | Status: new
Priority: blocker | Milestone: 4.4 EM & Plumi UI
Re-Design
Component: PlumiVideoProduct | Resolution:
Keywords: | Who will test this: And
-------------------------------+--------------------------------------------
Description changed by anna:
Old description:
> Changes to the publish form will be based on wireframes currently in
> draft form here:
>
> STEP 1 https://cacoo.com/diagrams/cJTnu33fvZDW6awm
> STEP 2 https://cacoo.com/diagrams/DVWh4bsC7jvQLU3x
> STEP 3 https://cacoo.com/diagrams/vindYlDdkliwK6b9
> UPLOAD WIDGET https://cacoo.com/diagrams/q29RP4vsit1inEdM
>
> Steps 1 & 2 will be attempted in this ticket, except for embedding videos
> from other sites, which means changing the video content type (and the
> video template) in a lot of ways. We will attempt this later, along with
> functionality in Step 3.
>
> The new publish form will be based on the current skin.
>
> Most importantly we want to overhaul the way videos are uploaded and
> added to Plone, in order to address stability issues that have been
> occurring such as incomplete uploads.
>
> In order to make uploading more reliable, we want to separate the
> uploading process (the backend process, not the form) from the zope
> servers. Zope servers get restarted every few days and are generally busy
> collecting and serving many things. Our initial plan is to make the zope
> servers WSGI applications and build another WSGI application from
> scratch, that will manage the upload process. This will increase the
> reliability of the upload process, as it will not be tied up to a
> specific zope instance. It will also reduce strain on the zope servers by
> not having them wait for large files to get uploaded. Moreover, we have
> to lay the groundwork for the entire mechanism of the new upload form,
> e.g. structure, javascript, AJAX saving and uploading etc.
New description:
Changes to the publish form will be based on wireframes currently in draft
form here:
* STEP 1 https://cacoo.com/diagrams/cJTnu33fvZDW6awm
* STEP 2 https://cacoo.com/diagrams/DVWh4bsC7jvQLU3x
* STEP 3 https://cacoo.com/diagrams/vindYlDdkliwK6b9
* UPLOAD WIDGET https://cacoo.com/diagrams/q29RP4vsit1inEdM
Steps 1 & 2 will be attempted in this ticket, except for embedding videos
from other sites, which means changing the video content type (and the
video template) in a lot of ways. We will attempt this later, along with
functionality in Step 3.
The new publish form will be based on the current skin.
Most importantly we want to overhaul the way videos are uploaded and added
to Plone, in order to address stability issues that have been occurring
such as incomplete uploads.
In order to make uploading more reliable, we want to separate the
uploading process (the backend process, not the form) from the zope
servers. Zope servers get restarted every few days and are generally busy
collecting and serving many things. Our initial plan is to make the zope
servers WSGI applications and build another WSGI application from scratch,
that will manage the upload process. This will increase the reliability of
the upload process, as it will not be tied up to a specific zope instance.
It will also reduce strain on the zope servers by not having them wait for
large files to get uploaded. Moreover, we have to lay the groundwork for
the entire mechanism of the new upload form, e.g. structure, javascript,
AJAX saving and uploading etc.
--
--
Ticket URL: <http://plumi.org/ticket/529#comment:7>
Plumi <http://plumi.org/>
Plumi - FOSS Video Sharing Platform
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
