Hi Carsten,

For sure it will be - but I want first to run some more tests and to 
wait feedback from the users, to be 150% sure that the fix does not 
introduce any new bug.

Regards,
Bogdan

Carsten Bock wrote:
> Hi Bogdan,
>
> short question:
> Will this also be ported to the 1.3 branch?
>
> Thank you,
> Carsten
>
>
> Am Montag, den 18.02.2008, 07:07 -0800 schrieb Bogdan-Andrei Iancu:
>   
>> Revision: 3723
>>           http://openser.svn.sourceforge.net/openser/?rev=3723&view=rev
>> Author:   bogdan_iancu
>> Date:     2008-02-18 07:07:23 -0800 (Mon, 18 Feb 2008)
>>
>> Log Message:
>> -----------
>> - fixed critical bug - DB operations do not have any feedback on the contact 
>> state, so DB data may be lost during short DB outages.
>>
>>   The temporary lost of lost DB connectivity leads to lost of contacts in 
>> DB: if DB insert or update fails, the contact will be anyhow marked as SYNC 
>> and never again inserted or updated to DB.
>>   This applies for both modes WRITE_THROUGH and WRITE_BACK. The fix extends 
>> theWRITE_THROUGH mode - if the realtime insert/update fails, the contact 
>> will be handled on timer, as in WRITE_BACK mode - the DB op will retry till 
>> success.
>>
>>   Delete operations do not provide feedback as a failed delete is not 
>> considered critical (no data is lost).
>>
>> Modified Paths:
>> --------------
>>     trunk/modules/usrloc/ucontact.c
>>     trunk/modules/usrloc/urecord.c
>>
>>
>> This was sent by the SourceForge.net collaborative development platform, the 
>> world's largest Open Source development site.
>>
>> _______________________________________________
>> Devel mailing list
>> [email protected]
>> http://lists.openser.org/cgi-bin/mailman/listinfo/devel
>>
>>     
>
>
>   


_______________________________________________
Devel mailing list
[email protected]
http://lists.openser.org/cgi-bin/mailman/listinfo/devel

Reply via email to