Ideally we wouldn't have to record data that's never read. This may be an extreme case, but some users will want to know the response on an upload, while some will just want to make sure the status is ok. I'd rather not anticipate too many use cases when writing the strand and the model because I might end up with code that's never used. If the bead was responsible for both recording the response and exposing it to the user, we wouldn't have to do that.
Perhaps a better example is permissions. I already have an Upload bead. Now I want an alert to pop up if the user is not permitted to upload. I'd like to be able to add a 'CheckPemissionsOnUpload' bead. Right now I don't see how to do that, instead I would probably have to replace 'UploadBead' with 'UploadButCheckPermissionsBead'. This takes us away from composition and forces inheritance. Maybe we don't need to modify class definitions. I think it's enough to modify the bead instance. In JS we could simply replace the function, and in flash we could maybe replace the whole original bead with a flash.utils.Proxy. But this will make things a bit complicated to read and maintain. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-FileUploaderWithResponseData-tp63051p63139.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
