I know the whole concept of scratch your own itch is a core concept of Apache, but this is a topic that I believe need a lot of input from the community at large, particularly those doing enterprise development.
I have spent a large part of the past 4 years doing Flex development specifically to work within a portal environment, and there are some definite challenges surrounding working within that environment. One of the major issues is that of persisting the state of the Flex application. In a portal environment, one of the core concepts is the idea of being able to bounce around between pages and having your portlets hold their state so that when you go back to them, you can pick up right where you left off. With a large Flex application, this is nay to impossible. Sure there are all kinds of tricks you can do with LSO's, deep-linking, etc. to simulate it, but I would like to see some of the more enterprise focused functionality like this be brought into the framework, or at least taken into consideration so that it is not quite so cumbersome. Unfortunately, I also realize that in order to accomplish this in the most elegant manner, we would likely need changes to the runtime itself. :-( Regards, Nick Collins
