xuzhenbao

@pnoltes Thanks for your review。The coming days/weeks, I will revise this PR according to your review comments.

> Place the implementation in libs/netstring and ensure that the lib file name is celix_netstring and the lib name is netstring with a Celix::netstring alias. The lib should depend on...

@pnoltes Do you have a development plan for EventAdmin？ If no, I'd like do it. And I have a question about netstring serialization. If we use netstring to serialize celix_properties,...

> What I remember from the experimental event admin impl is that we struggled with when a Event object could be destroyed and who should destroy it. How about define...

@pnoltes Do you have any plans to merge [type_support_for_properties](https://github.com/apache/celix/tree/feature/type_support_for_properties)? The event properties might need to support 'byte' type arrays property. Additionally, according to the OSGI specification [133.9](https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.event.html#d0e47619),event properties should support...

> Will the technology used for remote be plug-able and how? Maybe something like a distribution provider (as is used in Apache Aries, see https://aries.apache.org/documentation/modules/rsa.html) to make adding a new...

To remote event admin, I have the following ideas. First of all, the remote distribution provider should be pluggable, and its interface definition is as follows: ~~~ typedef struct celix_event_remote_provider_service...

> Considering the RSA approach, will event delivery be expensive? Yes, this is a weakness of RSA, maybe it can be solved by improve RSA, such as supporting long links,...

> Does the Event Admin need to be aware of remote events? I was considering the possibility that a Remote Event Admin could register an EventHandler with "event.topics=*". This way,...

> Given that pubsub has already been removed, it this PR already done? @xuzhenbao Thanks for the reminder. Maybe I need to plan a time to update this PR.