Hi there,
our implementation is in production :)
but has not yet been open sourced due to other tasks consuming time :(
it has solved all problems enumerated above...and I think it would be much
better to have one crypt implementation than two!
i'll ask the pavel that does the open-sourcing for
Hi Elena,
On Mon, Sep 22, 2014 at 11:32 PM, Elena Stepanova
wrote:
> As one of two first responders to all external MDEV bug reports, I'm not at
> all thrilled with the idea of assigning bugs automatically based on
> components.
>
> First, reporters are likely to choose wrong components, which
Very good news
Em terça-feira, 23 de setembro de 2014, Jonas Oreland
escreveu:
> Hi there,
>
> our implementation is in production :)
> but has not yet been open sourced due to other tasks consuming time :(
>
> it has solved all problems enumerated above...and I think it would be much
> better
Hi guy :) thanks for answering so fast!
there's others two mdev too that i sent some patchs
1) mdev-6766
some status variables counters, and two variables to 'tune' try_lock of
query cache, query_cache_write_timeout and query_cache_read_timeout, the
today value is hard coded to 50ms, some benchmark
Hi there,
we just managed to get the problems solved much faster as assumed. Thanks to
the community!
Perhaps it makes sense to have just one crypto implementation to do not confuse
users.
You can find our Source Code under: https://github.com/eperi-GmbH/server . As
fork of the actual 10.1 Code
=] nice, i will try soon
2014-09-23 15:50 GMT-03:00 Elmar Eperiesi-Beck :
> Hi there,
> we just managed to get the problems solved much faster as assumed. Thanks
> to the community!
>
> Perhaps it makes sense to have just one crypto implementation to do not
> confuse users.
> You can find our Sou
6 matches
Mail list logo
