Steve,
That's some interesting stuff you're doing.
If I understand it correctly, you're doing everything with web scripts in the Flex browser client, correct? How did you handle authentication? Are you using the flex-sdk from the Alfresco SVN or the WSDL stuff?
As far as 3.0 is concerned, I'd love for Alfresco to add BlazeDS or GraniteDS as an option for the service layer for interactive clients like Flex. Heck, Adobe did it for their Adobe Share platform which uses FDS and Alfresco (damnit Adobe, share it with us!). XML is easy to deal with but is quite poor from a performance standpoint. Integrating BlazeDS is something I'm researching right now - but I'm not a Java guy. Exposing all those Spring framework Beans to remoting would probably be a significant undertaking for such a newbie as myself.
I'm quite new to Alfresco, and Jan's Oposoro kit has helped me immensely because I haven't had the experience in writing web scripts on the backend. But that's a scripted client - not a Flex front-end (which I'm working on). I'd rather not have to write 90 files for 30 separate service calls. That seems to be the same route that many people are going down (portability is excellent). Personally, I'd rather expose the framework through AMF3 for performance reasons.
Anyway, it's great to hear additional people are working on Flex-based clients with Alfresco. I'm in the process of building a Flex (browser and AIR) client, so this is all quite interesting to me.
Drop me a msg offline (jbradley at postcentral dot com) if you're interested in collaborating in any manner. Not sure if you're stuff will be sourced or if it's screenshots of an internal job. I'm not too much of a data guy - way more on the design and interaction side of things.
There certainly aren't that many of us.
cheers,
jon
That's some interesting stuff you're doing.
If I understand it correctly, you're doing everything with web scripts in the Flex browser client, correct? How did you handle authentication? Are you using the flex-sdk from the Alfresco SVN or the WSDL stuff?
As far as 3.0 is concerned, I'd love for Alfresco to add BlazeDS or GraniteDS as an option for the service layer for interactive clients like Flex. Heck, Adobe did it for their Adobe Share platform which uses FDS and Alfresco (damnit Adobe, share it with us!). XML is easy to deal with but is quite poor from a performance standpoint. Integrating BlazeDS is something I'm researching right now - but I'm not a Java guy. Exposing all those Spring framework Beans to remoting would probably be a significant undertaking for such a newbie as myself.
I'm quite new to Alfresco, and Jan's Oposoro kit has helped me immensely because I haven't had the experience in writing web scripts on the backend. But that's a scripted client - not a Flex front-end (which I'm working on). I'd rather not have to write 90 files for 30 separate service calls. That seems to be the same route that many people are going down (portability is excellent). Personally, I'd rather expose the framework through AMF3 for performance reasons.
Anyway, it's great to hear additional people are working on Flex-based clients with Alfresco. I'm in the process of building a Flex (browser and AIR) client, so this is all quite interesting to me.
Drop me a msg offline (jbradley at postcentral dot com) if you're interested in collaborating in any manner. Not sure if you're stuff will be sourced or if it's screenshots of an internal job. I'm not too much of a data guy - way more on the design and interaction side of things.
There certainly aren't that many of us.
cheers,
jon
