Matt-Esch commented on issue #214:
URL: 
https://github.com/apache/pulsar-client-node/issues/214#issuecomment-1120560916

   I'm not sure what your full use case is but you might want to look at 
https://github.com/ayeo-flex-org/pulsar-flex - I haven't looked at it properly 
yet because it doesn't seem complete but it might be easier to extend or 
complete enough for your use case.
   
   I'm generally very dissatisfied with the c++ library let alone the node 
binding. I'm currently chasing down an issue with a race condition on close 
that causes a segfault. That should stir some level of caution around using 
this library and it clearly needs a lot of work. I think the reason for using 
the c api is that it's more stable between versions, so that also means not 
having the latest features. I did briefly look at using the C++ api because 
there are features missing for the async interface (that and the memory 
management is exceptionally painful).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to