Opened 11 years ago

Closed 20 months ago

#83 closed defect (migrated)

make OsiCpx thread safe

Reported by: mgalati Owned by: mjs
Priority: major Milestone:
Component: OsiCpx Version: 0.100.0
Keywords: Cc: magh@…


To make OsiCpx? thread safe, the env_, etc members should not be static. There should be an option (compile time?) that allows the user to define as many env_'s as necessary. And the vars should not be static. Using just one is not thread-safe.

Attachments (1)

osi-patch-83.diff (3.9 KB) - added by mgalati 11 years ago.

Download all attachments as: .zip

Change History (4)

Changed 11 years ago by mgalati

comment:1 Changed 11 years ago by stefan

I changed OsiCpx? in trunk to have one environment for each instance of OsiCpx?.

Do you also need a fix in stable ? It should be different since the changes in trunk changed the API (removed instance counting functions).


comment:2 Changed 11 years ago by mjs

Well, we can't change the API without bumping the minor version number. I'd guess if we do that, we'd take the base of the new stable branch from trunk anyway, wouldn't we?

comment:3 Changed 20 months ago by stefan

  • Resolution set to migrated
  • Status changed from new to closed

This ticket has been migrated to GitHub and will be resolved there:

Note: See TracTickets for help on using tickets.