My (limited) understanding of continuations is that they are the same as coroutines. There was a very interesting article in MSDN Magazine about extending.NET with coroutines by using fibers and native (C) interop.
"The exponential cost curve is mostly in detecting and communicating the Mistake and naming the change that is to be made. XP cannot change that curve, and indeed, XP takes that increasing cost curve neatly into account. So the first lesson I get is that one should not base a defense of XP on the ABSENCE of the curve, but rather on the PRESENCE of the exponential cost curve."
Did you even read enough of the article to see what SIP does? SIP uses RTP for the media trafic ("real time applications"). Using a "bulk data transfer" for call signaling seems quite appropriate to me. How quickly do you really need your phone to start ringing?
Also notice that SOAP uses HTTP for RPC. HTTP is hardly bulk anymore.
As far as I can see, there is no evidence for JBoss Consultancy and the Core Developers parting with bad blood between them.
Why would having two organizations instead of one commiting their business idea to open source Java enterprise development be a bad thing for the community?
Slashdot Mirror
My (limited) understanding of continuations is that they are the same as coroutines. There was a very interesting article in MSDN Magazine about extending .NET with coroutines by using fibers and native (C) interop.
"The exponential cost curve is mostly in detecting and communicating the Mistake and naming the change that is to be made. XP cannot change that curve, and indeed, XP takes that increasing cost curve neatly into account. So the first lesson I get is that one should not base a defense of XP on the ABSENCE of the curve, but rather on the PRESENCE of the exponential cost curve."
Also notice that SOAP uses HTTP for RPC. HTTP is hardly bulk anymore.
Why would having two organizations instead of one commiting their business idea to open source Java enterprise development be a bad thing for the community?