Hi,
I added some comments inline, and my wish list at the bottom...
Andrew Borley wrote:
A few things:
- Python extension - could re-jig the core to allow Python components
to not require a .componentType side file. Not necessary, but nice to
have.
+1, it will make a difference in terms of usability.
We may also want to implement a way to pass structured data to Python
scripts in addition to simple types (using Python ElementTrees for example).
- PHP extension - if we want to include this we need to add reference
& property support to components and a client API (a locateService
method)
+1, it would be great to bring the PHP extension to the same level of
function as the Ruby and Python extensions.
A side note: In addition to the injection of properties and references
into components, we currently provide a locateService method to clients.
This has been implemented for Ruby and Python, and we could very well
follow the same pattern for PHP, but I'm wondering if we could simplify
even more and just bind a global variable (some form of global variable
"injection") to the services available in the current composite instead
of forcing the client to call a locateService function or method. Any
thoughts on this?
- Samples
- do we include BigBank?
+1 to include BigBank, and maybe model the Web client part as an SCA
composite as well (in PHP if the PHP extension is ready).
SupplyChain?
+1, how about using SupplyChain to illustrate the integration of
composites developed in multiple languages, C++, Ruby or PHP and Java
for example (or maybe we can use BigBank instead for that).
- Tests
- Do we want an equivalent of the sdotest app for SCA?
+1, more and more tests, integrated in the build system so people can
just test with a "make check".
Andy
On 9/25/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
There have been significant changes since our last C++ release so I
think we
should plan for an M2 release in the next couple of weeks. We have
updated
to the latest assembly model, built a basic extension mechanism and
now have
extensions for Ruby, Python, PHP. Functionally this seems like good
content
for a new milestone but there will still be significant work items to
complete before we can cut a release.
Let's use this thread to note the items to be completed and get
volunteers
to do the work. So for starters:
- Persuade someone to volunteer as Release Manager
We can check this one, Thanks Andy for volunteering :)
- Update Licence text in source files to the new Apache wording
(Pete)
- Update release build scripts for linux and windows
- Documentation
- Developer build instructions
- New language extensions
- Release notes
- Samples
- new samples for Ruby/Python??
+1 to all of these!
I have a question on the samples, I'm not sure what to think about it.
Do people prefer to see the same sample implemented in multiple
languages? or different samples per language because they will fit
better with the particular language or will relate better to some well
known samples in that particular language space? I had initially started
with the same sample but I'm wondering if it's the right approach... Any
good ideas?
Other items from my wish list added at the bottom...
Let's discuss the work items here and create a wiki page with a
checklist.
Cheers,
--
Pete
Here are a few more items I care about:
- Good scripting support (Ruby, Python, PHP) to lower the bar for people
who want to write and integrate useful SCA components in a few lines of
script.
- REST support. We have the beginning of a REST support with Axis2C (on
the server side only now). I was thinking that we could complete this or
come up with an even lighter implementation directly as an Apache httpd
module.
- Speaking of Apache httpd, docs describing how to Tuscany / httpd + the
Axis2C axis2_mod. The Axis2c mini HTTP server is nice but we should make
sure that we can run with the real thing :)
- Easy packaging and deployment. Maybe simplify and open our
tuscany-root folder structure to allow people to choose the structure
that best fits their environment.
- Support for an identified level of the SCA assembly, binding and C&I
specs - 0.96? with a doc listing the limitations.
- One more scripting language, Javascript using Mozilla Spider-monkey?
- A small footprint with build options allowing people to build just
what they need (we've already started to some of these options to our
build).
- A sample showing how to turn existing C and/or C++ code into an SCA
component.
- Real life samples, talking to Google, Yahoo and Amazon Web Services
for example.
- A single helloworld sample?
- Platforms: Linux, Windows (VC++ express? VC6, or VC7?), and Mac OS-X.
- Dependencies: Axis2C 0.94 if it's out soon. Stdcxx as a build option.
- Finally docs, docs, docs :) The docs Pete listed above plus short user
how-to kind of docs to help people set up their environment, install or
build our runtime, write and run their first SCA app.
- A few short design docs describing the key aspects of our design (e.g.
our extensibility story) for people who want to understand how the
runtime works and contribute to it.
I'd better stop writing now, that's already a lot :). We probably cannot
do everything in this list, but as I said at the beginning, it's just a
wish list :)
Thoughts?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
