| < Previous by Date | Date Index | Next by Date > |
| Thread Index | Next in Thread > |
|
hi all,
in
RequestContext::getTransactionId()
{ return mOriginalRequest->getTransactionId(); }
i think the better way
is use one member varible to store this transaction ID. and add one
member funciotn.
void RequestContext:
setTransactionId(const Data &id )
{
m_transactionID= id;
}
const Data &
RequestContext: getTransactionId(const Data &id )
{
return m_transactionID;
}
Proxy should call RequestContext: setTransactionId
when it create RequestContext.
because in ACK RequestContext,
mOriginalRequest->getTransactionId() != transactionID. And when we try to
send asyns message in ACK request, when
it call RequestContext::getTransactionId(), it return an id
which is not AcK's transaction id, and in proxy it won't found match
RequestContext to process
async
message. 2008-06-07
hongsion
发件人：
resiprocate-devel-request@xxxxxxxxxxxxxxx
发送时间： 2008-06-06 01:01:55
收件人：
resiprocate-devel@xxxxxxxxxxxxxxx
抄送：
主题： resiprocate-devel Digest,
Vol 50, Issue 2
Send resiprocate-devel mailing list submissions to
resiprocate-devel@xxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
or, via email, send a message with subject or body 'help' to
resiprocate-devel-request@xxxxxxxxxxxxxxx
You can reach the person managing the list at
resiprocate-devel-owner@xxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of resiprocate-devel digest..."
Today's Topics:
1. memory leak fix to resiprocate-1.3 branch (Dmitry Semyonov)
2. Re: memory leak fix to resiprocate-1.3 branch (Scott Godin)
3. Re: [reSIProcate-users] Roadmap for 1.4? (Karlsson)
------------------------------------------------------------
From: Dmitry Semyonov <dsemyonov@xxxxxxx>
To: resiprocate-devel@xxxxxxxxxxxxxxx
Subject: [reSIProcate] memory leak fix to resiprocate-1.3 branch
Date: Wed4 Jun 2008 21:10:15 +0400 (MSD)
Guys,
Shouldn't [r7745] be merged into resiprocate-1.3 branch?
[r7745] http://svn.resiprocate.org/viewsvn/resiprocate?view=rev&revision=7745
--
...Bye..Dmitry.
------------------------------------------------------------
------------------------------------------------------------
From: "Scott Godin" <slgodin@xxxxxxxxxxxx>
To: <dsemyonov@xxxxxxx>
<resiprocate-devel@xxxxxxxxxxxxxxx>
Subject: Re: [reSIProcate] memory leak fix to resiprocate-1.3 branch
Date: Wed4 Jun 2008 13:59:47 -0400
Yes it should.
Scott
-Sent from my Blackberry mobile device.
----- Original Message -----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxx <resiprocate-devel-bounces@xxxxxxxxxxxxxxx>
To: resiprocate-devel@xxxxxxxxxxxxxxx <resiprocate-devel@xxxxxxxxxxxxxxx>
Sent: Wed Jun 04 13:10:15 2008
Subject: [reSIProcate] memory leak fix to resiprocate-1.3 branch
Guys,
Shouldn't [r7745] be merged into resiprocate-1.3 branch?
[r7745] http://svn.resiprocate.org/viewsvn/resiprocate?view=rev&revision=7745
--
...Bye..Dmitry.
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
------------------------------------------------------------
------------------------------------------------------------
From: Karlsson <boost.regex@xxxxxxxxx>
To: "Byron Campen" <bcampen@xxxxxxxxxxxx>
Subject: Re: [reSIProcate] [reSIProcate-users] Roadmap for 1.4?
Date: Wed4 Jun 2008 22:42:15 +0800
Does there has any plan to support XCAP?
Thanks
2008/4/9 Byron Campen <bcampen@xxxxxxxxxxxx>:
> I have been thinking, and I think the project would benefit with
> just a little more direction (nothing to heavy though). I have identified a
> small number of large-ish tasks that I think would be useful; I would like
> everyone (esp the users) to take the time to look them over and let us know
> which ones are most important to you. (If you feel that something important
> is missing from the list, please let us know also.)
>
> * More efficient handling of large numbers of TCP connections (ie, the C10K
> problem)
> * Complete update of supported headers/params
> * More documentation
> * UAS 100rel support (in DUM)
> * client outbound support
> * "Safety nets" for TUs
> **Timeout for server transactions if TU fails to respond within a
> certain time-frame (configurable)
> **Allow TUs to abandon uncompleted transactions easily
>
> Best regards,
> Byron Campen
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/
------------------------------------------------------------
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel |