<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Namespaces on sillysky.net</title>
    <link>https://sillysky.net/docs/nyssr/namespaces/</link>
    <description>Recent content in Namespaces 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/namespaces/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CWellKnownNID</title>
      <link>https://sillysky.net/docs/nyssr/namespaces/cwellknownnid/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/namespaces/cwellknownnid/</guid>
      <description>Some namespaces are used by the kernel or supplied plugins. The definition of the namespace IDs and their names is done in this class.&#xA;ID Function SYSTEM The most important namespace, always present TRANSPORT Namespace for network functions, always present when the network plugin is loaded TCP Namespace for the transport layer, always present when the TCP plugin is loaded TEST Namespace for TESTS, always present when the test plugin was loaded REMOTE_SKIN Namespace for the RemoteSkin UI </description>
    </item>
    <item>
      <title>INamespace</title>
      <link>https://sillysky.net/docs/nyssr/namespaces/inamespace/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/namespaces/inamespace/</guid>
      <description>A namespace provides a working environment for a plug-in, application, or microservice. It provides threads, registers targets, and has a local nano service registry. It encapsulates this environment from other namespaces so that, for example, hundreds of instances of the same application can operate simultaneously in the same node.&#xA;A number of namespaces are always registered in a node. However, the initialization of all packages is asynchronous. So it can happen that the own package is initialized, but the namespace is not available yet.</description>
    </item>
    <item>
      <title>INamespaceFactory</title>
      <link>https://sillysky.net/docs/nyssr/namespaces/inamespacefactory/</link>
      <pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://sillysky.net/docs/nyssr/namespaces/inamespacefactory/</guid>
      <description>Namespace creation is a complex process. Therefore, a factory is used for this purpose, the namespace factory. This factory is registered as a service in the service registry.&#xA;Get the factory The factory is fetched as a singleton from the service registry:&#xA;final INamespaceFactory nf = CServiceRegistry.getInstance() .getService(INamespaceFactory.class); As always, make sure that the service starter of your package has a dependency on the INamespaceFactory to ensure that the factory already exists.</description>
    </item>
  </channel>
</rss>
