Just send first increment about IMM wrapper out, will discuss on the design and
come up with something generic that coud be used to go with all IMM API.
The aim of first increment are:
- One IMM C API will be represented by one C++ class
- Get rid of void pointer, pointer to poiter or complicated input parameters
- Provide easy and simple interfaces to set/get IMM info
---
** [tickets:#2149] log: refactor handling IMM in log service **
**Status:** accepted
**Milestone:** 5.17.08
**Created:** Fri Oct 28, 2016 12:25 PM UTC by elunlen
**Last Updated:** Wed Apr 12, 2017 01:31 PM UTC
**Owner:** Vu Minh Nguyen
This ticket intends to do refactor stuffs related to IMM handling in log
service.
More details will come later.
With first look, we see many places using IMM APIs, and refering to IMM OI
handler. It would be very good if we could move this into one or several files
that are purely dedicated to IMM handling, with a well-defined API.
---
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
