<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Thanks Galder and Pedro. I'll implement
them as you suggested!<br>
Cheers<br>
On 2017-11-03 6:02 AM, Galder Zamarreño wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4D39A03B-F258-4A03-B017-E785DCAD5983@redhat.com">
<div class="ApplePlainTextBody">At first glance, I'd agree with
Pedro.<br>
<br>
<blockquote type="cite">On 2 Nov 2017, at 16:07, Pedro Ruivo
<a class="moz-txt-link-rfc2396E" href="mailto:pedro@infinispan.org"><pedro@infinispan.org></a> wrote:<br>
<br>
Hi,<br>
<br>
IMO, I would separate the concept of counter and
configuration.<br>
<br>
Even if an user doesn't create many counters, I think most of
them will <br>
share the same configuration. As a bad example, if you want to
counter <br>
oranges and apples, you're going to use the same
configuration... <br>
probably :)<br>
<br>
In addition, it is symmetric to the cache DMR tree. This would
reduce <br>
the learning curve if the user is already used to cli (i.e
create caches).<br>
<br>
Cheers,<br>
Pedro<br>
<br>
<br>
<br>
On 02-11-2017 12:33, Vladimir Blagojevic wrote:<br>
<blockquote type="cite">Hey guys,<br>
<br>
How do you anticipate users are going to deal with counters?
Are they<br>
going to be creating a lot of them in their applications,
say dozens,<br>
hundreds, thousands?<br>
<br>
I am asking because I have a dilemma about their
representation in DMR<br>
and therefore in the admin console and potentially wider.
The dilemma is<br>
related to splitting the concepts and the mapping between
counter<br>
configuration and counter instances. On one end of the
possible spectrum<br>
use, if users are going to have many counters that have the
same<br>
configuration then it makes sense to delineate the DMR
concept of the<br>
counter configuration and its counter instance just like we
do for<br>
caches and cache configuration templates. We deal with cache<br>
configurations as templates; one could create hundreds of
caches from<br>
the same template. Similarly, we can do with counters. On
the other end<br>
if users are going to create very few counters then it
likely does not<br>
make much sense to separate counter configurations from its
instance,<br>
they would have one to one mapping. For each new counter,
users would<br>
just enter counter configuration and launch an instance of a<br>
corresponding counter.<br>
<br>
The first approach saves resources and makes large counter<br>
instantiations easier while the second approach is easier to
understand<br>
conceptually but is inefficient if we are going to have many
counter<br>
instance.<br>
<br>
Thoughts?<br>
<br>
Vladimir<br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
<br>
</blockquote>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</blockquote>
<br>
--<br>
Galder Zamarreño<br>
Infinispan, Red Hat<br>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
infinispan-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></pre>
</blockquote>
<p><br>
</p>
</body>
</html>