This content has been marked as final. Show 5 replies
we almost dumped flash because this ONE class is completely jacked. it works horribly and has no feedback. doesn't work on https, corrupts the headers, fails on certain filesizes, etc.
Adobe REALLY needs to re-build this class.
Personally, I don't think the Flex team listens to people's issues. They think Flex is almost perfect and they just need to tweak things here and there.
I agree. This class and whole host of others.
I'm using Flex for a few applications and one is constantly battling with things that other tools have solved years ago. One ends up having to either re-invent things or find hacks or build core level classes to circumvent these issues.
In my opinion, Flex is not ready for prime time and the IDE most diffinately is not ready for prime time. It totaly suck and makes the whole development experience painful.
It worked fine for me and it does get a response, look at this topic where I wrote it done:
What worked for you?
The fact that you got the server response?
How about exceptions thrown by the server?
How about the MIME type that the server receives?
I did a small application that uploads a file to the server every hour. If the server response that a login is required to upload the file, it goes to a login page to do the login and retried to upload the file.
I got the server response in order to know if the file did upload correctly or not (I have to send more form data than just the file). I didn't try the mime type since it's not relevant for my application and usualy this information is not very trust worthy anyways.
I'm not sure what you mean with exceptions, if you are referring to HTTP errors, I think there is an event for that, but I used the IOError event for this, and it seems to work good also.