On 09/03/15 13:56, Julien Danjou wrote:
> Hi fellow developers,
>
> It'd be nice to achieve a 1.0 release for tooz, as some projects are
> already using it, and more are going to adopt it.
>
> I think we should collect features and potential bugs/limitations we'd
> like to have and fix before tha
So another idea.
I know kazoo has/had the following:
https://github.com/python-zk/kazoo/pull/141
"Add shared locks and revocable shared lock support"
It might be nice if tooz had support for that (the kazoo PR was rejected
since there just wasn't enough maintainers in the kazoo project to
su
Julien Danjou wrote:
On Mon, Mar 09 2015, Joshua Harlow wrote:
Another idea; provide some way for tooz to handle the heartbeating (instead of
clients having to do this); perhaps tooz coordinator should take ownership of
the thread that heartbeats (instead of clients having to do this on there o
On Mon, Mar 09 2015, Joshua Harlow wrote:
> Another idea; provide some way for tooz to handle the heartbeating (instead of
> clients having to do this); perhaps tooz coordinator should take ownership of
> the thread that heartbeats (instead of clients having to do this on there
> own)?
> This avo
On Mon, Mar 09 2015, Joshua Harlow wrote:
> One that I can think of off the top of my head would be to have `join_group`
> and associated functions have the ability to automatically create the group if
> it does not exist already (instead of raising a error and then having the user
> deal with the
Julien Danjou wrote:
On Mon, Mar 09 2015, Joshua Harlow wrote:
One that I can think of off the top of my head would be to have `join_group`
and associated functions have the ability to automatically create the group if
it does not exist already (instead of raising a error and then having the us
Another idea; provide some way for tooz to handle the heartbeating
(instead of clients having to do this); perhaps tooz coordinator should
take ownership of the thread that heartbeats (instead of clients having
to do this on there own)? This avoids having each client create there
own thread (or
Let's do it,
One that I can think of off the top of my head would be to have
`join_group` and associated functions have the ability to automatically
create the group if it does not exist already (instead of raising a
error and then having the user deal with the failure themselves).
I'm also
Hi fellow developers,
It'd be nice to achieve a 1.0 release for tooz, as some projects are
already using it, and more are going to adopt it.
I think we should collect features and potential bugs/limitations we'd
like to have and fix before that. Ideas, thoughts?
Cheers,
--
Julien Danjou
;; Free