We ran into this problem when we had an app that was using flash. We essentially created a short lived, one time use token that the javascript part of the app could ask for. It then gives it to the flash part of the app that invokes the upload. Here's the binary api I'm talking about: http://docs.jivesoftware.com/apireferences/latest/javascriptapi/osapi.jive.binary.osapi.jive.binary.html
On Wed, Jan 25, 2012 at 6:00 PM, Dan Dumont <ddum...@us.ibm.com> wrote: > It looks like shindig has a pretty significant issue here in that posting > file attachments through the proxy does not seem possible. > > From what I've read online, passing a form element to a native xhr in FF > and chrome will create a multipart mime post for you to the target. In IE > you have to use a flash plugin or something. > I think even supporting FF and Chrome would be an issue though, as we > treat POST_DATA to the makeRequest call as a string... > > and osapi.http.post goes through RPC so that seems like it will be > impossible to ever get to work posting binary data. > > Anyone have any ideas, or run into this before?
