I'd like to see closer integration between the Tuscany Java and C++ runtimes, with seamless cross-runtime wiring, deployment, and composition. The application developer would write SCDL containing components with different implementation types, and the application would be deployed to a combination of both runtimes according to the hosting needs of the components. Users would see a single "federated" Tuscany runtime environment hosting multiple implementation languages and component types, rather than being aware of two Tuscany runtimes written in Java and C++ as they are at present.
Simon Andrew Borley wrote:
Hi everyone, Now M2 is finally available, we should start thinking about what we'd like to do next in Tuscany C++. There were quite a few items that were suggested for M2 that we ended up leaving out for time reasons and it would be good to progress the function we have in M2. Things I would like to do/see: - Add initial support for SDO handling in the Python extension (as an XML serialization) - Remove requirement for componentType side-files for Python components - Get the PHP extension up to the level of the Ruby/Python extensions - perhaps by using the SCA for PHP stuff (http://www.osoa.org/display/PHP/SCA+with+PHP) - Improve the samples for the scripting languages (nebulous! does anyone have any good ideas?) - A sample showing the different languages working together. - A standalone REST binding - we can do a limited REST via the support in Axis2C, but I think it would be cool to have a real binding.rest that we can host in HTTPD. Please join in with your own thoughts/plans! Cheers Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
