Package com.iizix.server


package com.iizix.server
  • Class
    Description
    An implementation of a common end point for an Editor, Server or Monitor.
    This class is used to trace binary data to an output stream.
    The halt watchdog of a server exit: armed when the server begins to dispose for an exit, it halts the JVM with the exit code when the dispose has not ended within its time, so that a restart or an update the administrator asked for happens even when a module, the worker or the logger hangs on the way out (order CC-SERVER-RESTART-UPDATE-V5; NetPhantom's inactivityKillServer is the idea).
    The Server Application Loader interface, used by the Server but also the Distribution compiler.
    Interface for Server End Points.
    The type of end-point.
    Interface for plug-ins used to create a new end point.
    Interface used in the server to listen to creation of new end points.
    The server log history listener interface.
    The interface to the Server instance, whether running in a JakartaEE Application Server or stand-alone using another web server and/or WebSocket implementation.
    Error enum used when validating an App ID with locale support.
    States of the server.
    Interface for a listener used for the Server Admin functionality.
    Listener for the server dispose events.
    Interface that the server uses to redirect a request of a client to another server using the load balancer.
    Server using Jetty to serve a Run Configuration launch of an application from Eclipse.
    Class to handle localized messages for the server.
    The server log's listener that forwards entries to the Windows NT Event Log (CC-SERVER-RESTART-UPDATE-V5, stage F; NetPhantom's DefaultEventExit filter): SEVERE becomes an error event, WARNING a warning event, INFO an informational event only with the level NTEventLogListener.Level.INFO; CONFIG through FINEST never go.
    The level of the start option.
    The plug-in loader class checking for plug-in dependencies in a Module project.
    A PrintStream adds functionality to another output stream, namely the ability to print representations of various data values conveniently.
    Class used to specify a redirection server when the load balancer is enabled and a client connects to a server that should not process the request.
    The exit-code contract between the server process and whatever supervises it: the POSIX iiziServer.sh loop, the Windows iiziServer.bat loop, the Java service wrapper under SrvAny, the systemd unit and iiziGo's development-server launch (order CC-SERVER-RESTART-UPDATE-V5, the owner's rulings of 2026-10-11 at 19:05 and 19:30).
    What a connected client is told when the server exits (CC-SERVER-RESTART-UPDATE-V5, the owner's texts of the survey's section 8): the WebSocket close reason of the close code GCloseCodes.CC_SERVER_RESTART, "iz!4006!text", one text for a Browser and one for iiziRun on Cordova, where a page cannot be reloaded and the app is restarted instead.
    The license system of a started iiziServer, for its licence counter (com.iizix.server.user.LicenseCounter, LICENSE-V2-DESIGN.md 6.2) and through it for ServerAdmin's licence status line: ServerShell.getLicenseSystem() is package-private, and the counter lives in com.iizix.server.user beside ActiveUserSessions.
    The server logger implementation.
    The main class for an Server session running in the Server.
    The Server Shell.
    Why an exit request of ServerShell.requestExit(int, String) is refused.
    Who supervises the server process: what relaunches it when it exits with ServerExit.RESTART, and runs the updater first at ServerExit.UPDATE_RESTART.
    The static holder of the ServerShell instance that the server calls to initiate the value with at start-up time.
    The server's side of a graceful Windows service stop (CC-SERVER-RESTART-UPDATE-V5, stage-native): under the service wrapper (-supervisor wrapper) a daemon thread polls the file "server.stop" in the server's current directory, which the wrapper writes when SrvAny signals a service STOP; the server then asks itself to stop - exit code 0 through its dispose, every client told - instead of being killed.
    The iiziServer in Standard Mode.
    The statistics class is used to track information about what is going on in the server in terms of min/max/average values, I/O data amount and throughput, etc.
    Additional information that is stored for history entries for server statistics.
    A worker thread class for the server.