We need to add a new page or modify an existing page so that a user can pre-upload materials (Full list here, https://github.com/SenecaCDOT-BigBlueButton/bigbluebutton/blob/master/bigbluebutton-client/src/org/bigbluebutton/modules/present/ui/views/FileUploadWindow.mxml#L116). They should only be able to upload those file types.
When a meeting is started URLs to the pre-uploaded materials need to be attached to the create API call. The format of the url should be bbbman.senecacollege.ca/SenecaBBB/presentation/m_id-ms_id-sample.ppt. We then use a url rewriter to change the URL to bbbman.senecacollege.ca/SenecaBBB/presentation.jsp?p=m_id-ms_id-sample.ppt. The JSP can then validate the user if they are trying to download the material themselves or if the meeting is currently running it will just return the contents of the file.
For documentation on the API call for pre-uploading slides see, http://code.google.com/p/bigbluebutton/wiki/API#Preupload_Slides.
We need to add a new page or modify an existing page so that a user can pre-upload materials (Full list here, https://github.com/SenecaCDOT-BigBlueButton/bigbluebutton/blob/master/bigbluebutton-client/src/org/bigbluebutton/modules/present/ui/views/FileUploadWindow.mxml#L116). They should only be able to upload those file types.
When a meeting is started URLs to the pre-uploaded materials need to be attached to the create API call. The format of the url should be bbbman.senecacollege.ca/SenecaBBB/presentation/m_id-ms_id-sample.ppt. We then use a url rewriter to change the URL to bbbman.senecacollege.ca/SenecaBBB/presentation.jsp?p=m_id-ms_id-sample.ppt. The JSP can then validate the user if they are trying to download the material themselves or if the meeting is currently running it will just return the contents of the file.
For documentation on the API call for pre-uploading slides see, http://code.google.com/p/bigbluebutton/wiki/API#Preupload_Slides.