Hi, It seems like we will soon have to support several flex client using different server versions and I was wondering whether there were any good practices out there. Let me share w/ u my first thoughts: I was thinking to quickly switch into using spring on the server side (something that is long due around here anyways), and use DI to selectively wire up the right server implementation (assuming of course, I have 1 common interface to all clients). I have not digged much this direction but I think that's feasible depending on a token load one implementation rather than another one (with the assumption that I know all the implementation of that interface at design time. So I guess I could define them all in my appcontext config file and somehow switch it at run time. Anyhow, If you guys have any link/ref that can help me out there, I will take it! thanks.
Now what's left is the trigger/the token for the switch. I.e: I need to be able to differentiate between the different clients. I could use the user name and password and maybe use a custom java adapter that would pick that up from the session or I dont know where, and call my right implementation. I dont know how else I could do it w/o the custom java adapter?? any idea? Would the custom java adapter idea still work with LCDS where you are dealing w/ assemblers?? A last thing is that it would be cool not to have to use the username and password as the way to tell the different clients. (for several reasons: not all apps have auth, even if auth is present, you need to find out which company does that belong and my app might not host all the user locally...etc...). Instead it would be cool to have that sent as an http header/additional param , the same way you get the username and password. Is this possible in flex today ?? Thanks Cheers--
