Please note this site is going to be replaced with the new design very soon - some logistical/version info on this site is out of date. The new site can be found here.
Please note specifically: new releases page (dir), new mailing list (google group), new subversion hosting (googlecode)
(note last updated: 6/10/08

Kamaelia

Nuts & Bolts | Components | Tools | Cookbook | Systems
wiki actions :( EDIT | printable | Recent Changes | Dev Console | Sitemap/Index )
guest191856


Home, News
Dev Console

How, Why
Project Blog
Summer of Code

Documentation
Download
SVN (web)
Sourceforge page

Project Admin
License

Contact Us

  Page Tags

No tags are defined for this page yet - how would you classify/think of this page? Add your notes below!

Project Task Page: Axon ThreadedComponent API Change

Status: Completed
Current Developers: MH
Current "inflight" dev location: /branches/private_MH_axon_threads
Start Date: 13 April 2006
Expected End Date: n/a
End Date: 4 May 2006
Date this page last updated: 22 February 2007
Estimated effort so far: 15

Description

To change the design of ThreadedComponent so that when writing a component based on it, it is almost identical to writing a normal component (just leaving out the yield statements).

The existing design required the component writer to access queue objects to send and receive data, rather than use the self.dataReady(), self.send and self.recv() methods they would use for a normal component.

In the process, thread safety should also be improved, and the ability to add and remove inboxes and outboxes on the fly (ala AdaptiveCommsComponent) should be implemented.

Benefits:

Inputs

Relevant Influencing factors:

Outputs

Expected

Actual

Realistic possibilities arising as a result of activity on this task

Need to make access to CAT threadsafe too.

Task Log

Discussion

Distinction between activity-creators and non activity-creator components removed (the scheduler would stop if there wasn't at least one activity-creator microprocess running). This was no longer necessary as there was no longer a postman microprocess (a non activity-creator). Removing support for this from the scheduler simplified things, making implementing support for the new design threaded components (and later quiescence optimisations) easier.

-- Matt Hammond, 22 February 2007


Your tags for this page: If you had set UserPreferences (name & email) and validated them (simple single click in your email), you would be able to define personal tags

Versions: current , 1 , 2


(C) 2005 Kamaelia Contributors, including the British Broadcasting Corporation, All Rights Reserved,
This is an ongoing community based development site. As a result the contents of this page is the opinions of the contributors of the pages involved not the organisations involved. Specificially, this page may contain personal views which are not the views of the BBC.


This web site is powered by the same code created for the bicker manor project. For more details, contact Michael Sparks at BBC Research directly (cf contact)