It makes sense to me. So the better way is still providing the
`updateXXX` methods to `PulsarClient`. As for how to detect the
connection info (e.g. service URL) changes, it's determined by the
user's implementation. For example, the current AutoClusterFailover
polls with a fixed interval.
We can
+1 (binding)
* verify checksum and signatures
* build from source (Ubuntu 20.04 WSL)
* verify artifacts on Windows (`pulsar.dll` and `pulsarWithDeps.a` for
both x86 and x64 architectures)
* verify rpm, deb, apk packages in x86_64 architecture (`libpulsar.so`
and `libpulsarwithdeps.a`)
All the ver
+1 (binding)
Thanks,
Yunze
On Wed, Jan 25, 2023 at 4:22 PM Enrico Olivelli wrote:
>
> +1 (binding)
>
> Enrico
>
> Il giorno mer 25 gen 2023 alle ore 09:14 Nicolò Boschi
> ha scritto:
> >
> > +1 (binding)
> >
> > Thanks,
> > Nicolò Boschi
> >
> >
> > Il giorno mar 24 gen 2023 alle ore 20:11 Mich
+1 (binding)
Enrico
Il giorno mer 25 gen 2023 alle ore 09:14 Nicolò Boschi
ha scritto:
>
> +1 (binding)
>
> Thanks,
> Nicolò Boschi
>
>
> Il giorno mar 24 gen 2023 alle ore 20:11 Michael Marshall <
> mmarsh...@apache.org> ha scritto:
>
> > +1 (binding)
> >
> > Thanks,
> > Michael
> >
> >
> > On
+1 (binding)
Thanks,
Nicolò Boschi
Il giorno mar 24 gen 2023 alle ore 20:11 Michael Marshall <
mmarsh...@apache.org> ha scritto:
> +1 (binding)
>
> Thanks,
> Michael
>
>
> On Tue, Jan 24, 2023 at 10:13 AM Andrey Yegorov
> wrote:
> >
> > I am starting VOTE for the proposed implementation of PIP