[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Quixotic thought #57: Software salvation via JCSP


Summarizing, the idea has been tossed around that a 
demonstration product would "prove" the merits of CSP 
to the world:

> the possibility of persuasion by developing the kind of "product" for 
> which there is already widespread interest. 

Here's my own idea of the ideal demonstration: a wireless 
telephone, implemented entirely in one high level language, 
(either occam or java), both hardware and software.  The 
hardware should be asynchronous.

This would generate interest from a number of communities. 
Telecom is hot right now. Seamless integration of software/hardware 
would get the attention of the co-design crowd.  Asynchronous h/w 
design is considered difficult, is very quiet (no clock synchronization) 
and low power.  CSP based design could unify it all.  Maybe with Adrian's
Continuous CSP, you could even do the analog design.  

Think of it! The entire design in one language...OK, so I'm a dreamer.

Someone already mentioned 
> Quantel: my speculation (again) is that a webserver shown to be 
> deadlock/livelock-free on empirical and mathematical grounds would 
> attract more interest and lead to diffusion of CSP-inspired design 
> doctrine and JCSP-based design methodology. The members of this group 
> could accomplish such a task, though it might require a more 
> collectivistic orientation than many are used to, or 
> comfortable with. 
> Roy
> -- 
> Roy Wilson 
> E-mail: designrw@xxxxxxxxxxxxxxxx
> http://members.bellatlantic.net/~designrw/index.html
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> On 10/20/00, 9:58:06 AM, M_Boosten 
> <mboosten@xxxxxxxxxxxxxxxxxxx> wrote 
> regarding Re: A path for CSP-based:
> > Hi all,
> > topic: ...introducing CSP in industry...
> > Quite a while ago, Andrew wrote:
> > > So: unless you get in at the start, the (perhaps apparently
> > > insignificant) costs of transferring are simply too high. 
>  In an ideal
> > > world CSP would be a nice refinement to our development 
> process, but at
> > > the moment there are more pressing needs.  Perhaps that is worth
> > > remembering - you're not introducing CSP to people who 
> have nothing to
> > > do all day, but to people who already have a stack of 
> good ideas that
> > > need trying out when there's time available.  Busy busy 
> busy.  So no
> > > more emails from me ;-)
> > I agree, this is one of the main problems of introducing 
> any new idea,
> > including CSP.
> > Cheers,
> >       Marcel