Hi,
With current LOG Agent design, if N log clients open the same log stream, it
will create N log stream object, instead of refering to one.
I am going to change that point, all log clients will share same LOG stream
object. That stream object only closes when no client refer to it.
Will send an V2 patch when done, and I will add more description for each class
for more readability.
/Vu
---
** [tickets:#2412] log: refactor handling log client database in log agent**
**Status:** review
**Milestone:** 5.17.08
**Created:** Tue Apr 04, 2017 12:08 PM UTC by Canh Truong
**Last Updated:** Tue Apr 25, 2017 08:56 AM UTC
**Owner:** Vu Minh Nguyen
In log agent, there is a link list holding all log clients of an application
process. Also, in each log client, there is an additional link list holding all
log streams which belongs to each log client.
Adding, modifying or deleing the link lists' elements or on sub-items of the
client dabases are distrubuted in a lot of places, this could easily cause
troubles regarding race condition, deadlock, or risks when adding code that do
changes the databases.
So, this ticket intends to remove that concern by doing:
1) Centralizing read/write accesses to the database to one place with its
private mutex
2) Use C++ containters to contain and handle databases
And will push the ticket in 02 increments:
1) Convert agent code to C++ without touching any existing logic (looks like
what AMF has done it in [#1673])
2) Do #1 and #2 above
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
