Thanks everyone.

I've read all the replies, and I might understand something.
(Though it seems that discussion goes to beyond my current
understanding in the middle of this discussion threads)
To explore further, I become another owner of 'Programming
Clojure' :-)

For my second question, I'll keep thinking and repost question.
I'm really concern about concurrency of Clojure,
since the concurrency in my world means
_the C10K problem_, that is supporting simultaneous
10000 connections or over for networking applications.
(http://www.kegel.com/c10k.html)
In YAWS, Erlang have shown one solution, so I'm curios that
Clojure could be another viable alternative,
and that how well-suited Clojure is for that kind of concurrency.

My expectation is these:
1) For C10K problem (or C100K), application must not use
native threads. Big stack size means low concurrency
2) For application developer, thread model is easy to develop
and follow.
3) Therefore, underlying system should support
concurrency facility like micro-thread, lightweight process (in
Erlang)
, agent (in Clojure), or whatever.
In this case, underlying facility should have high-performance.
4) At the same time, there must be ways for connecting conceptual
gap between 2) and 3). In other words, the way for suspending current
execution of function, saving current execution snapshot
(normally native thread stack, but may be different),
and switching to other functions are needed when the request for I/O
should be blocked. It's important that the size of current execution
snapshot should be small, since it determine the degree of
concurrency.

After I invest some time to learn Clojure, I'll repost.

Thank you.

- cw
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to