At 06:50  8/4/01 -0700, Karthik Rangaraju wrote:
>Hi all, 

hi!

>      I'm new to the project and am excited to contribute. I've got a 
>couple of questions (this is my first open-source participation):
>Questions: 
>  How do you co-ordinate checking in new stuff? Do people develop locally
and 
>  email it to pre-approved/authorized folks? 

until they become committers - you may want to refer to the following web
pages for basic information.

http://jakarta.apache.org/site/getinvolved.html
http://jakarta.apache.org/site/guidelines.html

>  How does Apache decide whether or not to endorse new project ideas? 
>If I have an idea, how can I see if Apache would like to develop it? 

Well to be under the apache brand usually you need to 
* have some sort of guarentee that project will be sucessful
* have a community behind it 

However there is a recent project commons that is allowing newer projects
to grow inside apache. Join up to the mailing list and lurk there for a bit
to get a feel for it.

>Threading utilities: 
>      I've written classes for Mutex, Critical Sections, Djikstra Semaphores 
>      (also called counting semaphores) and Thread barriers. Avalon already 
>      has Mutexes and Locks, but you may find Djikstra semaphores and thread 
>      barriers useful 
>      Blocking queues: The most valuable threading utilities: I've got two 
>      versions: Bounded and boundless. A blocking queue blocks threads when 
>      trying to dequeue() from an empty queue. A bounded blocking queue
blocks 
>      threads trying to enqueue() to a full queue. 

sounds useful. 

>  Dispatch servers: 
>      I've got a dispatch and multi-dispatch (pipelined dispatch) server 
>      implementation. The basic idea is that you define a component (I
call it >      a ServerCommand) that the dispatch server manages. Each
component 
>      gets an in-queue and an out-queue and as jobs are put in its 
>      in-queue, the server hands it the job for processing and when done 
>      puts it in the outqueue. 
>      Multi-dispatch server extends this by creating a pipeline of commands 
>      by chaining in-queue and out-queues. You guys have Pipelines and 
>      kernels, not sure if they are different or not. I've not yet had a 
>      chance to dig deep 

looks good and similar to something I didi a while back (a cron/job server
based on ants notion of tasks).
>I'm also planning to write articles on the above for Java world. I hope
there 
>will be no copyright issues if you guys add the code to the Avalon project.

To be hosted in Apache CVS the code has to be copyright Apache.

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to