<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"></DIV> </DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>I’ve been looking through the presence module and have some questions
regarding the DB_ONLY mode of operation.</DIV>
<DIV> </DIV>
<DIV>Specifically the feature seems to rely on data not being written to hash
tables in certain areas of the code, as no checking is done to verify which
db_mode is being used.</DIV>
<DIV> </DIV>
<DIV>However there are places where the hash table is populated irrelevant of
the db_mode, for example the init code calls pres_htable_restore.</DIV>
<DIV>Additionally update_presentity seems to also manipulate the hash tables
indiscriminately.</DIV>
<DIV> </DIV>
<DIV>Am I missing something here, or is this a bug?</DIV>
<DIV> </DIV>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">Paul
</DIV></DIV></DIV></DIV></DIV></DIV></BODY></HTML>