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

CSP "encapsulated" in UML?



Gerald,

I've got some demo JCSP code that I want (eventually) to diagram in UML, 
so I'll be eager to see what you have/will come up with.

More generally, using UML might be another way of subverting "pure" 
OO-thinking: CSP as a kind of mind-virus (or meme?) transmitted via UML. 
Or not :).

Roy
-- 
 

(E-mail) jfastr@xxxxxxxxxxxxxxxx
(Business) JLWIP_Services
(Affiliate) HotDispatch

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 1/26/01, 6:02:35 AM, "Gerald H. Hilderink" <g.h.hilderink@xxxxxxxxxxxxx> 
wrote regarding RE: Java Live | January 9, 2001:


> Hi Andrej,

> > What?.... I think that this is an exaggeration, at least... I can provide
> > you with LONG list of people (more than just a "few") that are not only
> > specialists in the field, but have provided very essential contribution.
> > More essential contribution than just a book of average quality.

> Those people in the list provide very essential contribution to
> multithreading by building kernels, developing API's, building tools,
> writing books, and also showing design patterns on top of semaphores and
> monitors etc. Christopher shows design patterns in his book. The 
occam/CSP
> model also provides design patterns on top of multithreading. I guess,
> occam/CSP contributors are on that list as well.
> What troubles me is that Christopher waved away the occam/CSP model too
> easily. He may have not thought about those people who want to use
> concurrency in a more easy and reliable way at a high-level of 
abstraction
> (such as in object-orientation) than using low-level multithreading (that
> breaks object-orientation as Peter explained). I guess, the LONG list is
> SHORT after all, or not? That's why I used "few".

> My point is, multithreading is not the only style of living. My point is,
> the occam/CSP design patterns provide an easy and reliable style of 
living.

> Most people in the list don't know anything or know little about the
> occam/CSP model. Therefore, I am working on a UML/CSP model, which 
clarifies
> the ideas behind the occam/CSP model in their own way of thinking. The
> result of this work is astonishing, it improves concurrency in the UML in 
an
> elegant way, it also formalises concurrency in the UML, and 
code-generation
> becomes very straightforward. This takes at least three flies in one 
strike
> :-). Oh yes, it also shows that the concepts of CSP are very very OO. 
Oops,
> another fly killed! :-).

> Andrej thanks for your comment.

> Gerald.

> > -----Original Message-----
> > From: Andrzej Lewandowski [mailto:lewando@xxxxxxxxxxxxx]
> > Sent: Thursday 25 January 2001 15:12 PM
> > To: Java Threads mail group
> > Cc: Andre Bakkers
> > Subject: RE: Java Live | January 9, 2001
> >
> >
> >
> > > Thanks Rick,
> > >
> > > This T_Christopher seems to be a specialist in programming concurrent
> > > software. ***He is probably one of a few specialists in the world***
> >
> > What?.... I think that this is an exaggeration, at least... I can provide
> > you with LONG list of people (more than just a "few") that are not only
> > specialists in the field, but have provided very essential contribution.
> > More essential contribution than just a book of average quality.
> >
> > New on the mail group,
> >
> > Andrzej Lewandowski
> > Shelton, CT, USA