https://sillysky.net/docs/nyssr/messages/ Recent content in Messages on sillysky.net Hugo -- gohugo.io en Tue, 14 Oct 2025 00:00:00 +0000 https://sillysky.net/docs/nyssr/messages/cmessage/ Tue, 14 Oct 2025 00:00:00 +0000 https://sillysky.net/docs/nyssr/messages/cmessage/ CMessage is simply a container for the classes CEnvelope and CRecord. Constructors There are two constructors for the class. The first one takes over the given components: public CMessage(@NotNull final CEnvelope aEnvelope, @NotNull final CRecord aRecord); The second constructor takes a template and is actually a copy constructor: public CMessage(@NotNull final CMessage aTemplate); Stream Furthermore, there is a static method for reading the message from a DataInput stream: public static CMessage fromStream(@NotNull final DataInput aStream) throws IOException; Accordingly, there is also a method for writing to a DataOutput stream: https://sillysky.net/docs/nyssr/messages/imessagesender/ Tue, 14 Oct 2025 00:00:00 +0000 https://sillysky.net/docs/nyssr/messages/imessagesender/ The message sender is the service that can send messages. There are also methods for sending messages in targets, but these also use the message sender internally. The message sender is available as a service via the service registry. final IMessageSender messageSender = CServiceRegistry.getInstance() .getService(IMessageSender.class); Send messages The methods for sending messages are always executed in pairs. While one method receives a complete message, the second method always receives the components of the message.