QUESTIONS / ANSWERS

FAQ: nyssr.net & RemoteSkin

Frequently asked questions about nyssr.net, getting started, nodes, messaging, service discovery, edge computing, RemoteSkin, and licensing.

Getting started

How do I start with nyssr.net?

Start with the smallest useful system: one Java application, one node, and one message flow.

  1. Add the nyssr.net library to your project.
  2. Initialize the micro-kernel and a package with a service starter.
  3. Create and register a target.
  4. Start a second node and load a plugin containing a microservice.
  5. Send a message and handle its response.

The Getting Started guide walks through the complete first project.

How many nodes do I need?

One node is enough to develop and debug your first application. Add more nodes when you want to test distribution, routing, redundancy, or service placement. The programming model remains the same.

Can I turn an existing Java application into a node?

Yes. Add the nyssr.net runtime library and call the startup code at the application entry point. The existing application becomes a node that can communicate with other nodes, load plugins, and host services.

Turn a Java program into a node →

Nodes, connections, and the network

How do nodes find each other?

Nodes are connected through explicit connections. When a connection is established, the nodes exchange information about available services. Service registries can be distributed across multiple nodes for redundancy.

What happens when a connection is lost?

The node continues its local work. The runtime attempts to reconnect automatically at short intervals. When the connection is restored, interested targets receive a reconnect notification and can synchronize or resume their work.

Edge computing with resilient connections →

Do I need a central broker?

No. nyssr.net does not require a central broker, message queue, or cloud endpoint. Service registries, routing, and message handling are distributed across the node network.

Can nodes run behind a firewall?

Yes. A node can initiate connections to other nodes, and the network can operate across private IP spaces and firewalls. The node does not need a publicly accessible IP.

Configure nodes behind firewalls →

Messaging and services

What are active microservices?

An active microservice owns state and participates in its own message workflow. It can validate session tokens, coordinate with other services, and continue or stop work based on asynchronous replies. Active microservices are often created by factories. When the requesting target or node disappears, the system can notify the service and let it terminate its instance cleanly.

How does messaging differ from REST or JMS?

nyssr.net uses typed messages that travel between objects across the node network. The same message model works for local communication and cross-node communication. There is no separate HTTP layer, no REST endpoint mapping, and no JMS broker configuration.

Comparison with REST and Java messaging →

How are messages routed?

Messages are routed through the node connections. The routing considers the available topology and connection costs. Messages can carry priority, transport options, and reply instructions.

What is a service registry?

A service registry holds the mapping between a service name and its current location on the node network. Multiple nodes can host registries for redundancy and load balancing. Callers do not need to know where a service is physically running.

Redundant registries and service discovery →

Edge computing and local autonomy

What happens when the connection to the central site is unstable?

The local node can continue its work. Messages targeting remote nodes are queued or retried. The application controls how duplicates, stale data, and synchronization are handled.

Does the application need to implement reconnect logic?

No. The runtime handles reconnection automatically. The application can subscribe to reconnect notifications and decide what to do when the connection is available again.

Can I use nyssr.net for devices with limited resources?

The runtime is designed for Java applications on standard server and desktop hardware. For very small devices, the library overhead may be significant. The runtime is best suited for applications that already run on a JVM.

RemoteSkin

What client renderers does RemoteSkin provide?

RemoteSkin provides a Swing renderer. A Web renderer is planned around Material Design. The architecture keeps the UI description and application logic separate so renderers can evolve independently.

Which Swing features are supported?

Most standard Swing widgets are supported. Some advanced features, including internal frames, drag-and-drop, accessibility support, and Java 2D, are incomplete or still evolving.

Does a RemoteSkin application feel local?

For normal network latency, yes. Only a small amount of data is transferred to construct the UI. A noticeable delay generally appears only on very high-latency connections.

Can third-party widgets be integrated?

Yes. A widget provider can add a plugin and translate the RemoteSkin JSON protocol into calls to the widget API. The protocol can be extended for custom capabilities.

What is the future of the Java Swing renderer?

RemoteSkin will continue to be available as a Micro-UI technology for HTML/Web. The Swing renderer is no longer actively maintained for new development.

Architecture and design

How is nyssr.net different from other distributed platforms?

nyssr.net is a self-hosted runtime, not a platform service. It does not require a central cloud, broker, or orchestration layer. The programming model is object-oriented messaging rather than REST endpoints or JMS queues.

Design goals of nyssr.net →

What happens when a node is restarted or updated?

The node restarts its local services. Remote nodes detect the restoration of the connection. Applications that need to resynchronize state can respond to the reconnect notification.

Can I run multiple nodes on the same machine?

Yes. Multiple nodes on the same machine can communicate through the loopback interface. This is useful for development, testing, and running multiple services on one host.

Licensing

What is the license model?

nyssr.net is available under a free Community License for private, academic, experimental, development, testing, and staging use. Commercial use requires a paid annual license per productive node.

Are there any restrictions on downloads?

Downloads are currently public. The license terms define what constitutes permitted use, not a download gate.

Can I redistribute nyssr.net with my application?

OEM and embedded licensing is available for redistribution, embedding, SaaS, and hosting scenarios. Please contact us for details.

Where should I continue?

This page combines the former nyssr.net and RemoteSkin FAQs. New topics can be added as they come up.