<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Introduction to nyssr.net on sillysky.net</title>
    <link>https://sillysky.net/docs/nyssr/basics/</link>
    <description>Recent content in Introduction to nyssr.net on sillysky.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 14 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sillysky.net/docs/nyssr/basics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Messages</title>
      <link>https://sillysky.net/docs/nyssr/basics/messages/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/basics/messages/</guid>
      <description>Messages in nyssr.net are asynchronous and object-to-object. A target waits for incoming messages, processes them, and can send further messages without blocking the rest of the network.&#xA;This simple mechanism supports observers, notifications, services, broadcasts, requests, and responses.&#xA;Request and response A message travels from a sender to a receiver. Both addresses are carried in the envelope. When the sender wants an answer, it sets the wantAnswer flag. The receiver can then return a response after processing the request.</description>
    </item>
    <item>
      <title>Namespaces</title>
      <link>https://sillysky.net/docs/nyssr/basics/namespaces/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/basics/namespaces/</guid>
      <description>Namespaces are components of Nodes.&#xA;Each namespace has at least one thread, exactly one target registry, and exactly one nano service registry. They are the basis of applications, since applications with all their targets and local services must be executed multiple times and simultaneously in a node.&#xA;Target Registries Namespaces have a Target-Registry. Targets - the Java objects that can receive messages - are registered in these target registries. During registration, the targets are given a unique address.</description>
    </item>
    <item>
      <title>Nodes</title>
      <link>https://sillysky.net/docs/nyssr/basics/node/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/basics/node/</guid>
      <description>A node is a small Java runtime that participates in the nyssr.net network. Its microkernel is roughly 1.2 MByte and contains the messaging core, timers, threads, namespaces, and logging. Networking and other capabilities are loaded as plugins when the node starts.&#xA;One runtime, many roles Nodes are normally built from the same kernel and configured through their plugin list. The same container can therefore take different roles:&#xA;a registry or coordination node a node hosting application services a node connected to local databases or machines a client or development node The role is not hardcoded into the container.</description>
    </item>
    <item>
      <title>Segments</title>
      <link>https://sillysky.net/docs/nyssr/basics/segments/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/basics/segments/</guid>
      <description>All nodes of a company are part of a Segment .&#xA;The operation of multiple segments and the communication of objects between the segments is currently still experimental.</description>
    </item>
    <item>
      <title>Targets</title>
      <link>https://sillysky.net/docs/nyssr/basics/targets/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/basics/targets/</guid>
      <description>The class that programmers work with most often is the Target class. Targets are lightweight Java Objects that send and receive messages.&#xA;Registration To make this possible, they are registered in the Target Registry. Upon successful registration, a target receives an ID, the target ID (TID for short). It is possible to give constant TIDs to targets during registration, but usually a random ID generated by the target registry is sufficient.</description>
    </item>
  </channel>
</rss>
