To ensure the topic string is valid. Without enhancing the API I do not see a way to ensure the topic is valid. It would either have to happen an Event construction or at event send/post. But in both cases it would happen once for each Event.
Perhaps there is some justification to creating a Topic type that can be constructed once and used to create many events? If this is important to you, then I suggest an issue to discuss. We of coarse, then need someone to drive the change to the specification.
Dear Colleagues, Why is it necessary to validate the topic of an event each time an event is created? Would it not be better to be able to create a validated Topic Object and only have to validate the topic name once? We need and event bus
ZjQcmQRYFpfptBannerStart
This Message Is From an Untrusted Sender
You have not previously corresponded with this sender.
ZjQcmQRYFpfptBannerEnd
Dear Colleagues,
Why is it necessary to validate the topic of an event each time an event is created? Would it not be better to be able to create a validated Topic Object and only have to validate the topic name once? We need and event bus that is efficient for high data
throughput on embedded systems, but do not want to use a nonstandard interface.
Sincerely,
James
--
Dr. James J. Hunt
CEO & Geschäftsführer
aicas GmbH
Emmy-Noether-Straße 9 ● 76131 Karlsruhe ● Germany
https://www.aicas.com
● Tel: +49 721 663968 22
USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim
Geschäftsführer: Dr. James J. Hunt
aicas incorporated
6 Landmark Sq., Ste 400 ● Stamford, CT 06901 ● USA
https://www.aicas.com
● Tel: +1 203 435 0521
aicas America limited
4023 Kennett Pike, Ste 810 ● Wilmington, DE 19807 ● USA
https://www.aicas.com
● Tel: +1 203 435 0521