[SIPSERVLET_SPEC-41] Concurrency issues remain in SipServlet 2.0v0.9 Created: 14/Mar/14 Updated: 24/Nov/14 Resolved: 24/Nov/14
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
I am worried that (in introducing our thread-scheduling solution in 18.3.2) we are ignoring a set of problems that will hit both container and application developers hard. Rather than rambling on, I will outline a use-case to illustrate the point:
Perhaps we do not have the time to fix the API or the specification. However, we may be able to outline a set of use cases that both app and container developers can consider when developing apps, perhaps in an appendix. As a bonus, in outlining these use-cases, we may be able to tighten up the spec a little.
|Comment by binod [ 09/Oct/14 ]|
|Comment by binod [ 13/Oct/14 ]|
Here is the proposed text we can add to the end of section 220.127.116.11
|Comment by binod [ 24/Nov/14 ]|
Section 18.104.22.168 has been modified to reflect the suggested change.