Change my mind again, it's now TerracottaClient since it actually starts up a
client when being instantiated and then provided access to the
ClusteringToolkit methods.
Thinking even further, maybe the toolkit should be accessible like this:
TerrracottaClient client = new TerracottaClient("localhost:9510");
ClusteringToolkit toolkit = client.getToolkit();
This would allow us to later be flexible in how the client is handled.
Thoughts?
On 26 May 2010, at 16:01, Geert Bevin wrote:
> Renamed ExpressToolkit into TerracottaToolkit now.
>
> If anyone has objections, please say so.
>
> On 25 May 2010, at 23:38, Geert Bevin wrote:
>
>> Yes, Taylor's Terracotta* suggestion has rapidly grown on me too
>>
>> --
>> Geert Bevin
>> Terracotta - http://www.terracotta.org
>> Uwyn "Use what you need" - http://uwyn.com
>> RIFE Java application framework - http://rifers.org
>> Flytecase Band - http://flytecase.be
>> Music and words - http://gbevin.com
>>
>> On 25 May 2010, at 22:38, Steve Harris <st...@terracottatech.com> wrote:
>>
>>> Was playing with the toolkit and with my hands on I now have the opinion
>>> that I like it like this.
>>>
>>> Cluster(ing)Toolkit toolkit = new TerracottaToolkit();
>>>
>>> I'm on the fence between Clustering and Cluster but could live with either
>>> way.
>>> That it way it reads like Terracotta has an implementation of the generic
>>> Clustering toolkit concept.
>>>
>>> I can live with the Terracotta name there because it's in the impl not the
>>> interface and others can create there
>>> own implementation if they so choose.
>
--
Geert Bevin
Terracotta - http://www.terracotta.org
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
