Ultrashock Forums - View Single Post

Polaco · 2009-06-09 #21

Oh!, for the tremendous joy of developers:
http://kb2.adobe.com/cps/405/kb405546.html
So, you can't upload multiple files secuentially in this way using URLLoader.
I guess in case you have to upload 100 images you must invoke 100 urlloaders at the same time.Instead of loading them secuencially.
Of course FileReference doesn't have this restriction, but doesn't send any session data so is usless for many people who has to upload files under an https environment or with authentication under plain http.
It's really strange the FileReference behavior since other flash.net objects works perfectly under same conditions. Either I can't understand this kind of extreme and unnecessary security restrictions that lumber the player API, developement tasks and the end user capabilities.
It would be great that Adobe reconsider all this tons of pointless restrictions and deliver a refactored API that has a common way to handle this kinds of things for the next flash player release. Which I hope it wouldn't be too far away from now and thus late.

just a wish...

	Polaco	2009-06-09 #21
	Last edited by Polaco : 2009-06-09 at 20:42. Oh!, for the tremendous joy of developers: http://kb2.adobe.com/cps/405/kb405546.html So, you can't upload multiple files secuentially in this way using URLLoader. I guess in case you have to upload 100 images you must invoke 100 urlloaders at the same time.Instead of loading them secuencially. Of course FileReference doesn't have this restriction, but doesn't send any session data so is usless for many people who has to upload files under an https environment or with authentication under plain http. It's really strange the FileReference behavior since other flash.net objects works perfectly under same conditions. Either I can't understand this kind of extreme and unnecessary security restrictions that lumber the player API, developement tasks and the end user capabilities. It would be great that Adobe reconsider all this tons of pointless restrictions and deliver a refactored API that has a common way to handle this kinds of things for the next flash player release. Which I hope it wouldn't be too far away from now and thus late. just a wish...