|
From: Sean M. <sea...@pr...> - 2002-02-05 16:31:12
|
At 11:04 05/02/2002 -0500, David Starr wrote: >I just took a look through the 0.6 code (still have to look at the NetBeans >editor component). I see that the XPipe XComponents element no longer has a >ScheduleType which was the bit that I was waiting on the code for to >complete my understanding. So with that missing, I guess I fully understand >XPipes now. Scheduling is back in primordial soup land in my head. I've been reading a lot about emergent behaviour, web services orchestration, XLANG etc. and think some more thinking time is in order before I put forward a proposal for scheduling. Ideas solicited! >Apart from what's in the development plan, there seem to be a number of >things left to take care of in the existing components: > - Parameter passing. > - Testing of pre- and post-conditions. > - Generalizing unit testing so that it extends to XPipes. > >Is there a plan for these? I know that my Java implementations don't >currently fit the 'unpack an XComponent' model. If it's desired to have >these implemented in Java, I could presumably rework a version in Java that >acts on unpacked components (although it's my personal preference to try and >avoid unpacking) and add some of the items mentioned above. These are on my list for this weekend. A side-effect of the parameter passing work will be that xc5 - the first "Exec" component will become functional. I'd really appreciate help getting the Ant build (build.xml) into shape David. If you get some time could you take a look at it? Sean |