Objectives: To allow a User to upload analysis logs (or any file in reality) for viewing by a selected community of users, typically those joined to a GoogleWave. After these logs are available to the Wave, a specialist may view and copy/paste from one or more of them to create and upload a Results File. The User then proceeds to Download the Results File to be used as instructed.
Normal HTTP Post or PUT requires the user to manage duplicate file names and would not solve the following issues (2-4): 1) a user may need to upload multiple files at different date/times 2) a given file may need to be uploaded more than once and each version still retained over time. 3) uploaded files 'belong' to the unique Wave from which they were uploaded. 4) any User may be associated with multiple Waves hosted on the same system. A) The upload GUI SHOULD control the client space problems and contribute the identity of the Wave and the User as factiods of the upload. B) The CGI used to receive the files SHOULD control the relocation of the temp files and thus the Wave and User information can be used to perform the relocation to the new public and persistent location. C) the Wave is not persistent but the uploaded files are, which creates the need to discover the existing uploaded files as the Wave is initiated (from the Host or Client?) and make them accessible to the Wave. D) Long term file management needs to be addressed; when to delete or archive? I have a Java applet to perform (A), but the Wave and User factiods needs to be added. Integration to GW is pending. Please relocate as appropriate; ? What group would be appropriate for this discussion? Jeff -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
