OK, thanks for your explanation, Chris.
FYI: I've organized all components around Pulsar here:
https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=1261350388
On Wed, Apr 20, 2022 at 11:48 PM Chris Bartholomew <
chris.bartholo...@kesque.com> wrote:
> Hi A
Hi Anonymitaet,
On 1, Starlight for JMS is technically a wrapper around the Java API.
However, JMS is a widely used client API specification so to call it a
client wrapper doesn't seem like the right classification to me. The Python
client is a wrapper around the C client, but we don't call that a
Hi Chris,
Thank you very much for providing useful information! I've added them all
to the sheet.
For categories, I have two quick questions:
#1. For Starlight for JMS [1]
I see you categorize it as "Client API". Does it make sense to categorize
it as "Client Wrapper"? (which is the same as the
Hi Pulsarers,
For the Ecosystem Page [1], we want to make it a place for the Pulsar
community to come together and share the components the community needs to
build better streaming data pipelines and event-driven applications.
So I've collected all Pulsar-related plugins and tried to re-catego
