Hi Juha,
have had any time to try the patch I sent? Thinking of committing it,
but no presence server environment at hand for me to try it quickly...
Thanks,
Daniel
On 9/7/11 6:59 PM, Daniel-Constantin Mierla wrote:
Hello,
On 8/30/11 7:43 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla
Daniel-Constantin Mierla writes:
have had any time to try the patch I sent? Thinking of committing it,
but no presence server environment at hand for me to try it quickly...
daniel,
sorry, i forgot about it. is it really a good idea to allow any etag?
would it be better to require that etag
Hello,
On 9/12/11 9:47 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
have had any time to try the patch I sent? Thinking of committing it,
but no presence server environment at hand for me to try it quickly...
daniel,
sorry, i forgot about it. is it really a good idea to allow
Daniel-Constantin Mierla writes:
By using ., the presence server will create a new e-tag, right? It is
not an update to an existing presence document, but creation of a new
one.
yes, it is considered a new presence document, which replaces an old one
if any. same as if a single ua crashes
Hello,
On 8/30/11 7:43 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
In the xmlrpc command, there was an etag value, have you tried with '.'
as etag?
i haven't tried with . etag yet. i'll try that tomorrow.
mi pua publish from different UAs on same presentity seems to
work ok,
i started to test sr presence and for some reason sr does not send out
any publish request when i issue one via pua_mi.
i have in route [xmlrpc_requests]:
xlog(L_INFO, Handling XMLRPC $rm from $si with body
$(rb{re.subst,/[\n\r\t]//g})\n);
set_reply_no_connect();
set_reply_close();
Juha Heinanen writes:
pua/send_publish() function and it spits out 418 in this piece of code:
presentity= search_htable(pres, hash_code);
if(publ-etag presentity== NULL)
{
lock_release(HashT-p_records[hash_code].lock);
return 418;
}
Hello,
On 8/29/11 8:49 PM, Juha Heinanen wrote:
Juha Heinanen writes:
pua/send_publish() function and it spits out 418 in this piece of code:
presentity= search_htable(pres, hash_code);
if(publ-etag presentity== NULL)
{
Daniel-Constantin Mierla writes:
looking at the xmlrpc command content, I see the E-Tag value set, for
the first publish, shouldn't it be empty and the presence server returns
the value to be used later for updates?
daniel,
my app that sends mi pua publish, takes etag from presentity table
On 8/29/11 10:06 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
looking at the xmlrpc command content, I see the E-Tag value set, for
the first publish, shouldn't it be empty and the presence server returns
the value to be used later for updates?
daniel,
my app that sends mi pua
Daniel-Constantin Mierla writes:
The presentity table is built when a PUBLISH is received, did you sent
another PUBLISH before so that you have a record in this table? Or how
was it added in this table so that you could get the etag value?
there are several sources that can send publish for
On 8/29/11 10:23 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
The presentity table is built when a PUBLISH is received, did you sent
another PUBLISH before so that you have a record in this table? Or how
was it added in this table so that you could get the etag value?
there are
Daniel-Constantin Mierla writes:
In the xmlrpc command, there was an etag value, have you tried with '.'
as etag?
i haven't tried with . etag yet. i'll try that tomorrow.
mi pua publish from different UAs on same presentity seems to
work ok, when UAs always use . as tag param.
-- juha
13 matches
Mail list logo
