Please allow update property value about gproc HOT 4 CLOSED

Actually, you can update a property value with gproc:set_value(Key, Value).

It could arguably be optimized using ets:update_element/2, but looking at gproc_lib:do_set_value/3, I'm more of a mind to slow it down a bit to make it safer instead.

from gproc.

Thanks for pointing on it! Going to use it in my app. what are consequences of usage of ets:update_element/3? Could we have single function which does "set or update" value for given key? If it doesnt fit into gproc nicely then please close this ticket with no prob.

from gproc.

The things gproc needs to check are:

• The property being updated belongs to the current process
• It's a pre-existing property (which also means gproc is monitoring the
  process)

Looking again, gproc_lib:do_set_value/3 could use update_element()
instead of insert(), since the Pid is part of the key. For unique names, it
has to ask the gproc server to do it, since the race condition cannot be
resolved in the client.

Implementing a set_or_update() could possibly have some performance
implications for counters or properties, but personally, I'm not that
excited about the semantics. I personally prefer being explicit about
creating vs updating objects.

2011/12/4 redbaron <
[email protected]

Thanks for pointing on it! Going to use it in my app. what are
consequences of usage of ets:update_element/3? Could we have single
function which does "set or update" value for given key? If it doesnt fit
into gproc nicely then please close this ticket with no prob.

---

Reply to this email directly or view it on GitHub:
#13 (comment)

from gproc.

Fair enough. Thanks for response.

from gproc.