search

imace / jetlang

Automatically exported from code.google.com/p/jetlang
0 stars 0 forks source link

what's the essential different between jetlang and java thread pool with queue? #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Sorry,I don't know where to ask the question,maybe this is not the suitable 
place to issue this question.
I am not understand the essential different between jetlang and java thread 
pool with queue.
according my understanding,the jetlang's channel is like the threadpool's 
runnable queue,message queue up in the channel is like runnable queue up in 
threadpool's queue.
are there essential different between the two beside the concept about actor 
model?

Original issue reported on code.google.com by ljw79...@gmail.com on 3 Jun 2012 at 12:20

GoogleCodeExporter commented 9 years ago 
There is a discussion group that is better suited for design and usage 
questions.

https://groups.google.com/group/jetlang-dev?pli=1

I'll take a shot at a basic answer.

Jetlang fibers guarantee sequential execution of events. It is similar to a 
single queue with a single consuming thread that executes all events. A jetlang 
channel is a conduit that allows for decoupling publishers and subscribers. A 
channel doesn't contain a queue at all. It maintains a list of subscriptions.  
The jetlang api gives you a robust publish/subscribe api for asynchronous 
messaging.

Original comment by mike.ret...@gmail.com on 3 Jun 2012 at 7:14