<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi Bobby,<br>
<br>
Thanks for the feedback, see my inline comments.</tt><br>
<br>
On 02/11/2013 06:32 PM, Bobby Smith wrote:
<blockquote
cite="mid:CAJQeEgsyan5HEBxhKOnu_whxe=WO8kQwa-NZRx24y62O38GsCg@mail.gmail.com"
type="cite">1) TCP fixes (async/non-blocking) -- I know these are
already on the list, but as we move more and more traffic to TCP
on older versions, we are seeing reduced performance and odd
deadlocks/socket problems from time to time</blockquote>
yes, this is a bit of a painful matter and it will be addressed in
the next release.<br>
<br>
<blockquote
cite="mid:CAJQeEgsyan5HEBxhKOnu_whxe=WO8kQwa-NZRx24y62O38GsCg@mail.gmail.com"
type="cite">
<div>
2) better support of RFC 6140 (the gruu fixes that saul
mentioned come to mind)</div>
</blockquote>
OK, if you also have examples of cases which do not work, please
fill in some bug reports on SF tracker - it will help the developers
in fixing things.<br>
<br>
<blockquote
cite="mid:CAJQeEgsyan5HEBxhKOnu_whxe=WO8kQwa-NZRx24y62O38GsCg@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>3) not really related to the release, but representation at
SIPNOC this year would be pretty awesome. A lot of people from
the standards bodies meet here (IETF), and seeing some pursuit
around sipconnect 1.1/2.0 would be great for the community IMO
as most of the people here offering competing choices are
vendors selling black box products, however there is asterisk
representation and everyone uses SER in one flavor on their
networks :).<br>
</div>
</blockquote>
Indeed, it will be interested and useful, and I would love to do it
if we find fonds to support the participation to such an event...as
OSS project, there is no much income to help with the participation
to various events.<br>
<br>
Best regards,<br>
Bogdan <br>
<br>
<blockquote
cite="mid:CAJQeEgsyan5HEBxhKOnu_whxe=WO8kQwa-NZRx24y62O38GsCg@mail.gmail.com"
type="cite">
<div>
<div><br>
<div class="gmail_quote">On Mon, Feb 11, 2013 at 10:38 AM,
Saúl Ibarra Corretgé <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="im"><br>
On Feb 11, 2013, at 12:38 PM, Saúl Ibarra Corretgé
wrote:<br>
<br>
> Hi Bogdan and team,<br>
><br>
> On Feb 9, 2013, at 7:40 PM, Bogdan-Andrei Iancu
wrote:<br>
><br>
>> Hi all,<br>
>><br>
>> According the the release policy (<a
moz-do-not-send="true"
href="http://www.opensips.org/Development/Development"
target="_blank">http://www.opensips.org/Development/Development</a>),
I would like to call for a brainstorming, ideas,
discussion, etc regarding what should be the roadmap for
OpenSIPS 1.10 - more or less, what new goodies should be
in 1.10 release (next major release).<br>
>><br>
>> The page is already ready (<a
moz-do-not-send="true"
href="http://www.opensips.org/Main/Ver1100"
target="_blank">http://www.opensips.org/Main/Ver1100</a>)
and pre-populated with the pending items from 1.9
release plus some items from my side .<br>
>><br>
>><br>
>> I would like to stat the discussion here, on
the mailing list first, to get from all community ideas
on what should be done in 1.10 - things to improve,
supporting new RFC/drafts, new functionalitites, etc.<br>
>><br>
>> So, please do not be shy and make your points
here ;).<br>
>><br>
>> Also we plan a second round of discussion /
selection via an IRC meeting (probably in 2 weeks or
so).<br>
>><br>
><br>
> You asked for it :-)<br>
><br>
> Here are 3 big items I think we should have in
OpenSIPS:<br>
><br>
> 1. Non-blocking TCP operations (this is already on
the list)<br>
> 2. "Outbound" support (RFC5626) - supporting this
may affect the design of point 1.<br>
> 3. WebSocket transport<br>
><br>
> As for bug fixes, there are a few that come to
mind:<br>
><br>
> 1. Proper routing of in-dialog messages when GRUU
is used. (the dialog should remember the path and
loose_route should route the message to the right place
even if an AoR is found in the contact, which happens
when GRUU is used. This is a problem if a user
re-registers while on a call and she chooses a different
inbound proxy, as the in-dialog requests would now
follow a different path).<br>
> 2. PUA module should refresh outgoing subscriptions
until told otherwise<br>
> 3. presence_xml should validate incoming PIDF
documents (validate them against the schema, that is).
Right now it doesn't, and if a client sends a broken
document then the aggregated PIDF document will also be
broken. Those broken docs should not be stored.<br>
><br>
> I can elaborate on any of the points in case there
are any doubts :-)<br>
><br>
<br>
</div>
Oh, since I'm here, let me add one more thing:<br>
<br>
- Get rid of the lumps or add a way to apply all pending
lumps to a message manually. This would fix a number of
issues that can now happen, like using engage_mediaproxy
and removing the SDP of a 183 response.<br>
<br>
<br>
Regards,<br>
<div class="im"><br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
</div>
Devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a>
</pre>
</blockquote>
</body>
</html>