App Kernel — OSGi bootstrap, configuration, logging, filesystem
The eight bundles that turn an Equinox framework into a LibreSocial peer before any social feature loads
(Source/org.lifesocial.core.main, .core.utilities, .core.logger, .core.filelogger, .core.filesystem,
.core.equinoxconsole, Source/com.common.utilities, Source/org.libresocial.launcher) plus the launch
descriptors (cnf/*.bndrun, build-logic/, Dockerfile, compose.yaml). Related:
plugin system, overlay and P2P framework, monitoring.
Purpose
The kernel is everything in the peer that is neither the overlay/storage stack (com.p2pframework.*) nor a
feature plugin. It owns the process, the on-disk layout, persistent configuration, the log stream and the
operator console, and publishes the services every other bundle assumes:
- Bootstrap and lifecycle. Start the framework, bring up the Eclipse runtime and SWT workbench and run
an
IApplicationwith no hand-writtenmain(); theLifeSocialcomponent binds the P2PFrameworkservice, creates the working directories, pushes application directory / current ring / ring-manager interval into it, and persists that state on shutdown. - Configuration. Three layers with different lifetimes: a read-only tuning file inside a bundle, a writable per-node XML state file, and launch-time framework properties.
- Logging, disk accounting, operator surface. A typed
ILogServiceover the OSGiLogService, a file logger on the sameLogReaderServicestream,ISystemfor storage directory / disk usage / cleanup, and an Equinox-consoleCommandProvidermapping_execute,_showall,_helplsonto the command router. - Platform abstraction.
com.common.utilitieskeeps path resolution, network-interface discovery and hierarchical properties free of OSGi, so they also work from static initializers and in the tester.
Current implementation (as of 2026)
Working tree at ce9b710a1 (2026-11-12, master). Counts from the current tree.
Directory (Source/…) |
Bundle-SymbolicName |
.java |
lines | @Component |
|---|---|---|---|---|
org.lifesocial.core.main |
org.lifesocial.core |
145 | 10 034 | 2 |
com.common.utilities |
com.common.utilities |
14 | 1 963 | 0 |
org.lifesocial.core.utilities |
org.lifesocial.utilities |
4 | 439 | 0 |
org.lifesocial.core.logger |
org.lifesocial.logger.component |
4 | 382 | 1 |
org.lifesocial.core.filelogger |
org.lifesocial.filelogger.component |
2 | 231 | 1 |
org.lifesocial.core.filesystem |
org.lifesocial.system.component |
3 | 280 | 1 |
org.lifesocial.core.equinoxconsole |
org.lifesocial.equinoxconsole |
1 | 135 | 1 |
org.libresocial.launcher |
org.libresocial.launcher |
2 | 96 | 1 |
Directory names and symbolic names drift apart (org.lifesocial.core.logger → org.lifesocial.logger.component) and the bndrun files select bundles by osgi.identity, so those names are load-bearing; 128 of the 145 files in core.main are the exported data model, three are the kernel itself.
Bootstrap chain
./gradlew runOsgi drives org.libresocial.buildtool.osgi-runtime in build-logic: DetectPlatformTask
writes build-conf/platform-description.json (OS sanitised to win32|macosx|linux, arch to
x86_64|x86|aarch64), the matching cnf/org.libresocial.launcher.${os}.${arch}.bndrun is selected — each
one -include:s org.libresocial.launcher.common.bndrun and adds only the platform SWT fragment plus
runblacklist entries for foreign-OS fragments — then syncRuntimeRepo publishes every subproject jar
into cnf/runtime-repo (index.xml, registered as OSGiRepository in cnf/build.bnd) and bnd 7.2.3
resolves with -resolve: beforelaunch and starts Equinox (-runfw: org.eclipse.osgi):
- start levels:
org.apache.felix.scr2.2.14 at 1;org.eclipse.core.runtime3.34.200 andorg.eclipse.equinox.http.servlet/http.jettyat 2;org.libresocial.launcherat 3;-runstartlevel: default=4for kernel and plugins. -runproperties: eclipse.product=org.lifesocial.ui.product, eclipse.noShutdown=true, osgi.console=localhost:10001;-runprogramargs: -consoleLog;-runvm: -Xms256m,-Xmx2g;-runee: JavaSE-17;-runtrace: true. runrequires pull the kernel bundles by identity plusrice.freepastry,com.p2pframework*and the gogo console stack.
Inside the framework, ApplicationRunnable (@Component(service = Runnable.class, property =
"main.thread=true")) instantiates org.lifesocial.ui.Application, an Eclipse IApplication, and calls
start(new SimpleApplicationContext()). That context is the minimal contract the SWT shell needs: empty
APPLICATION_ARGS, branding ids legacy.app/legacy-app, application id org.lifesocial.ui.application;
the launcher prints LibreSocial Launcher 1.0.0 and nothing else. The legacy path still exists in parallel:
org.lifesocial.ui/config/plugin.xml declares the org.eclipse.core.runtime.applications extension and the
product org.lifesocial.ui.product that eclipse.product selects. main.thread=true is metadata only —
the string exists in Equinox's EclipseAppDescriptor (main.thread/any.thread) and no class here reads it.
Container path
prepareContainerContext syncs cnf/*.bndrun, cnf/build.bnd and the runtime-repo jars into
build/container-context/ and renames biz.aQute.bnd-*.jar to bnd/bnd.jar. The image
(eclipse-temurin:21-jdk-jammy, libgtk-3-0, non-root libresocial user) runs
java -jar /opt/libresocial/bnd/bnd.jar run cnf/org.libresocial.launcher.linux.x86_64.bndrun, so the
resolver runs inside the container at start-up. compose.yaml publishes 8443 (web UI), 10001 (console,
host-bound to 127.0.0.1) and 9001 (Pastry). Since osgi.console=localhost:10001 would be unreachable from
outside the container, CI rewrites the bind host in the staged copy
(sed -i 's/^\([[:space:]]*osgi\.console=\)localhost:/\10.0.0.0:/', 00536649e, corrected in a94feb903).
The console default became 10001 — network port + 1000 — in 0967596b8; the tree's last commit (ce9b710a1)
only updates that value in .env. The data volume is commented out ("Enable volume after fixing the storage
backend"), so container state is ephemeral.
Application object
LifeSocial is @Component(name = "LifeSocial", immediate = true, service = ILifeSocial.class) and
implements ISaveConfigurationListener. activate() builds a LifeSocialConfiguration, reads
PropertiesContainer.CONFIG_FILE when it exists, mkdirs the working directory and P2PFramework, then
setupFramework(): setDebugMode(false), setApplicationDirectory(P2PFramework),
ringDispatcher.setCurrentRing(...), setRingManagerUpdateIntervall(...). The framework arrives as a DS
reference — @Reference(name = "Framework", policy = DYNAMIC, unbind = "unsetFramework") on a
setFramework(Framework) setter that also registers the component as a save listener; core.main reaches
com.p2pframework via Require-Bundle, never the other way round. deactivate() and any framework-driven
save() call saveConfiguration(): read the framework back into the configuration objects,
ringDispatcher.storeSettingsNow(), config.writeToFile(CONFIG_FILE).
The bundle also exports the platform's shared vocabulary: data.interfaces (Storable, Payload,
Header, StorageKey), the per-feature DTO packages, events (EventManagerCore, EventConstCore),
commands (ICommands, AbstractCommands, ICommandHandler) and commoninterfaces (Plugin, Observer).
Open defect. LifeSocial.getFramework() (lines 91–92) is return this.getFramework(); — a
self-recursive call ending in a StackOverflowError for its callers. Present since 88b9632df
(2013-12-16) and still at HEAD; SystemComponent.activate() depends on exactly that chain
(((LifeSocial) lifeSocial).getFramework().getConfiguration().getStorageDirectory(), with a TODO asking to
put the storage directory on ILifeSocial instead). Reported as observed, not fixed by this survey.
Configuration layers
| Layer | Where | Written at run time | Read by |
|---|---|---|---|
| static tuning | config/LibreSocialConfig.txt, bundle resource of org.lifesocial.utilities (99 lines) |
never | ConfigLoader (getResourceAsStream, throws if absent) — messagedispatcher, SignStorageDispatcher, SocialCache, monitoring, tester |
| node state | ~/.LibreSocial/config.conf (XML) |
LifeSocialConfiguration.writeToFile on save/shutdown |
readFromFile in activate() |
| launch properties | -runproperties, -runprogramargs, -runvm |
operator / CI | Equinox, Eclipse runtime, console |
AbstractConfiguration enforces by reflection that each subclass declares static final String SECTION, and
stores every value in a HierarchicalProperties under SECTION + key, so keys are path-qualified
(/FrameworkConfig/CURRENT_RING, /ApplicationConfig/ChatPlugin/refreshTime) and a plugin adds a section by
contributing a subclass. FrameworkConfiguration holds CURRENT_RING (UUID) and
RING_MANAGER_UPDATE_INTERVALL (30 000 ms), with DEFAULT_NETWORK_LOCAL_PORT = 9001; a 2026 fix matters on
first start, because set(key, null) into a ConcurrentHashMap crashed LifeSocial.activate().
The tuning file holds the platform's behavioural switches and is read verbatim today: storage
(replicationFactor = 4, CanYouProvideTimeOut = 7000, objectSizeCalculationEnabled = 1,
autoDeleteStorage = 0), capacity/heterogeneity (enableHeterogeneityAwareness = 1,
heterogeneityCacheSize = 50), the social-cache block (socialCacheEnabled = 1,
socialCacheUpdater = socialscore, socialCacheUpdateLimit = 2, socialCacheMUCLimit = 150), DSS tuning
(dds_split_size = -1, dds_linkedlist_consolidation = true, justParallel = 0, parallelity = 1,
combineParameter = 3), monitoring (autoStartMonitoring = 0, measuringData = 1,
socialMetricCollection = 1, monitoringToGnuplot/SQLite/Dat/CSV = 0, mobileNodes = 0), routing
(disablePIRouting = 1) and UX (autoFriendRequestAccept = 1, autoLiveChatInvitationAccept = 1,
autoVotingInvitationAccept = 1). Booleans are 1/0, parsed as value == 1; monitoring is off by
default since the 2026 stability pass.
PropertiesContainer supplies the constants: WorkingDir =
PlatformIndependence.getApplicationDataDirectory("LibreSocial") → ~/.LibreSocial (Linux),
~/AppData/Local/LibreSocial (Windows), ~/Library/Application Support/LibreSocial (macOS);
P2PFrameworkDir = WorkingDir/P2PFramework; CONFIG_FILE = WorkingDir/config.conf; timeouts
(RequestTimeout and SystemValidityPeriod 10 s, LoginTimeout 120 s, StandardWaitingTime 30 × 1200
tries); negative status codes −100…−114 and −130…−135; plugin ids and tokens. The Linux location keeps
being renegotiated: 17f4cda9f (2016-07-27, "changed path where storage is located on linux to avoid
problem with nfs") moved it to $PWD/.LibreSocial; the 2026 refactor returned to $HOME.
Logging, filesystem, console
LogServiceComponent (@Component(name = "LOG", service = ILogService.class)) forwards
info/warning/error/debug, with and without Class/Throwable, to the standard
org.osgi.service.log.LogService (DYNAMIC reference) and keeps recent entries for getLogEntries();
observers attach through registerLoggingClient. That buffer is now a bounded ArrayDeque of
MAX_LOG_ENTRIES = 5000, and the source comment records why: the unbounded ArrayList retained every
line, so a component spamming failed lookups (SignStorageDispatcher "Item not found") piled up tens of
millions of entries until the JVM died in a GC death spiral (d9ccc75b9, 2026-07-06).
FileLoggerComponent (@Component(name = "FileLogger")) implements LogListener, attaches to
LogReaderService in activate(), and writes <WorkingDir>/log/Lifesocial - <yyyy_M_d (H.m.s)>.log,
deleting a pre-existing file of the same name; isLogToScreen mirrors DEBUG, WARNING and ERROR to stderr
but not INFO. SystemComponent (ISystem) implements cleanUp(), getStorageDirectory(),
getDiskSpaceUsage(): it records the initial directory size, appends tracked directories to
WorkingDir/LSTrack.trk, and reports usage as current minus initial; cleanUp() deletes them only if
CleanUpLocalStorage is true, and it is false, so shutdown never discards node data.
EquinoxConsole (service = CommandProvider.class, symbolic name with singleton:=true) contributes
_execute, _showall, _helpls, _gethelpfor and getHelp(), delegating to the injected
ICommandsComponent and forwarding TimeoutException; since ba7b37a10 (2026-11-11) the plugin-side
command references are MULTIPLE/DYNAMIC and 14 bundles carry -dsannotations-options: inherit, so the
console keeps working with a partially satisfied plugin set.
Build and packaging
All eight bundles are Gradle projects applying osgi-bundle-conventions.gradle: Java 17 Adoptium toolchain,
sources in src, resources from resources and config, jar metadata from bnd reading a per-bundle
bnd.bnd, -dsannotations: * where DS components exist. cnf/build.bnd pins -runee: JavaSE-17 and
downgrades bnd's "classes found in the wrong directory" error to a warning. com.common.utilities is the
only kernel bundle with DynamicImport-Package: *; org.lifesocial.core still uses Require-Bundle for
org.lifesocial.utilities, org.lifesocial.logger.component, com.p2pframework, com.common.utilities
and rice.freepastry — the Import-Package lesson from 2008 never applied here. SWT 3.128 is wrapped as
bundles under bundle-wrapper/ (f523b23dc).
Design options and decision
The 2008 OSGi study states its options and decision explicitly; entries marked reconstructed are inferred from commits and comments.
- Monolith vs module runtime. The 2007 LifeSocial.KOM prototype shipped as one JAR with a hand-written
plugin monitor: new features required recompile and restart, the flat classpath gave no version
constraints, no runtime resolution and no information hiding, and shadowed versions surfaced as
LinkageError. Decision (2008): OSGi R4 with Eclipse Equinox; the alternatives named in the study were Knopflerfish (BSD), ProSyst mBedded Server and the Samsung/Hitachi runtimes, and Equinox won on the EPL licence, a current release (17.06.2008) and the Eclipse-based UI. The kernel is the residue of that split: service components instead ofmain(),LOG/ISysteminstead of static helpers, DS cardinalities (0..n,1..n,0..1,1..1; static vs dynamic) instead ofnew. main()vs product registry vs DS-launched application. Reconstructed: the launcher wrapper (6caddfdb9, 2026-06-08) exists because-runfwstarts the framework directly — no PDE launcher, no native executable — whileorg.lifesocial.ui.Applicationstill needs anIApplicationContext. Wrapping the product class in aRunnablecomponent plus a hand-built context made the shell startable from Gradle/Bndtools; the cost is two bootstrap paths and amain.threadproperty nothing consumes.- Kernel-instantiated vs service-injected framework. Reconstructed: binding the P2P framework through
a DYNAMIC
@Referenceis what lets overlay, storage and monitoring bundles be absent or replaced. The price shows up incom.p2pframework.Configuration, which hardcodes the LifeSocial directory to avoid the circular dependency: "Because of OSGI we need to include the LifeSocial directory directly. OSGI makes the life so much harder :(". - Configuration format. Reconstructed: path-qualified keys in an XML
HierarchicalProperties(rather than one.propertiesper bundle) let any bundle add/ApplicationConfig/<Plugin>/…without touching the kernel. Splitting read-only tuning (bundle classpath) from writable node state (per-user data directory) means an upgrade replaces defaults without destroying ring identity — and equally means tuning changes need a rebuild, which is why the tuning file is still a build artifact, not an operator file. - Data directory:
$HOMEvs$PWD. 2016 chose$PWD/.LibreSocialto dodge NFS-mounted homes in the lab; the 2026 refactor returned to$HOMEbecause the working directory is undefined once the peer is launched by Gradle, bybnd runor from a container. - Own facade vs pure
LogService. Decision (2008, kept): the app-facingILogServicegives typed levels and an observer API for GUI/console, while the sink is the standardLogService, so Equinox diagnostics and third-party listeners see the same stream and the file logger is an ordinaryLogListener. Price accepted in 2026: the history accessor has to be bounded. - Console exposure. Reusing the Equinox console instead of a bespoke admin socket keeps OSGi debugging
and application commands in one place and lets the tester drive the same
_executepath as an operator. The trade-off is an unauthenticated plain-text endpoint, hence thelocalhost:binding and the rewrite to0.0.0.0:10001only inside a container whose port CI publishes on127.0.0.1. - Java 7 vs Java 17. The 2025 documentation mandates JDK 1.7.0_80, Eclipse Indigo (Build 20110615-0604),
Java 1.6 source compliance on a JavaSE-1.7 execution environment and unlimited-strength JCE policy jars.
Decision (2026): migrate rather than pin — OpenRewrite
UpgradeToJava17(3a9e918d0), manual fixes, execution environments raised toJavaSE-17(6b651a1e1), OSGI-INF XML translated to annotations (189018957); reconstructed driver is that no supported JDK 7 image exists for containers. The migration stays half-declared: bundles sayJavaSE-17, the container base is Temurin 21, and-runee: JavaSE-17is only the resolution floor. - Monitoring: centralized, gossip, or overlay-tree. The kernel carries only the switches
(
autoStartMonitoring,measuringData,monitoringTo*); the choice against a centralized collector and against unstructured gossip belongs to the SkyEye line of work — a monitoring tree derived deterministically from the identifier space (branching factor β, depth O(log N)), commutative and associative aggregation, coordinator replacement plus same-level gossip under churn, at ~1 032 B/min/peer on Pastry against 26 294 B/min/peer on Chord, error ±0.1 against ±0.7 for push-sum gossip, converging in ~2 minutes at 30 s intervals with β = 4. See monitoring.
Technical details
Declarative Services graph (kernel).
| Component name | Provided service | References (all DYNAMIC with unbind) |
|---|---|---|
LifeSocial (immediate) |
ILifeSocial |
Framework → com.p2pframework.Framework |
LOG |
ILogService |
org.osgi.service.log.LogService |
FileLogger |
LogListener |
logReader (LogReaderService), ILogService (bound, unused) |
SystemComponent |
ISystem |
LOG (ILogService), LifeSocial (ILifeSocial) |
equinoxconsole |
org.eclipse.osgi.framework.console.CommandProvider |
COMMANDS → ICommandsComponent |
ApplicationRunnable |
Runnable (main.thread=true) |
none |
All references being DYNAMIC is what lets bundles stop in any order, at the price of NullPointerExceptions
when a component is used after unbinding. SystemComponent also carries a dead overload
unsetLogService(ILifeSocial) that nulls the lifeSocial field — misleading, since that reference's unbind
method is unsetLifeSocial.
Ports and start levels.
| Port | Owner | Source |
|---|---|---|
| 9001 | Pastry bind/bootstrap | FrameworkConfiguration.DEFAULT_NETWORK_LOCAL_PORT, mirrored by com.p2pframework.Configuration, which probes a free port with NetworkHelper.findAvailablePort |
| 10001 | Equinox console (telnet) | -runproperties: osgi.console=localhost:10001; compose maps LIBRESOCIAL_CONSOLE_HOST_PORT |
| 8443 | web UI / REST | WebProvider.PORT; the fallback loop walks the cause chain because Jetty 12 wraps BindException (e49c67c60) |
| 8080 | webprovider instance manager | INSTANCEMANAGER_PORT |
On-disk layout (Linux). ~/.LibreSocial/config.conf (node state, written on save/shutdown),
~/.LibreSocial/LSTrack.trk (directories tracked by SystemComponent),
~/.LibreSocial/log/Lifesocial - <yyyy_M_d (H.m.s)>.log, and ~/.LibreSocial/P2PFramework/ as the
com.p2pframework application directory, holding log/ and storage/<ringId>/ for local PAST/Kryo data.
Shared helpers (com.common.utilities, 14 classes, zero DS components by design — a plain library usable
from static initializers such as PropertiesContainer). PlatformIndependence (OS/arch detection, data
directory); NetworkHelper (rewritten 2026: interface enumeration, loopback-safe IPv4 selection,
findAvailablePort, BOOTSTRAP_ADDRESS resolving www.hhu.de) — the code where the multi-loopback failure
Imam documented on Debian/Ubuntu had to be fixed, feeding com.p2pframework ring configuration and the STUN
bundle; HierarchicalProperties/Node/XMLHelper (path keys, XML import/export — the backing store of
config.conf); BlockingExecutor; FileUtils, ArrayHelper, ImageHelper, MathUtil,
Soundex/WeightedLevenshteinDistance, Tree.
Evolution and supersession
- 2007–2008 — monolith. One application with its own plugin monitor; layered model overlay → storage/replication → dispatcher → information cache → plugins → UI, with plugins pulling from the cache.
- 2008 — OSGi re-modularisation. Equinox 3.4, bundles, Declarative Services. Lessons recorded there:
prefer
Import-PackageoverRequire-Bundle(still violated byorg.lifesocial.core), activate each command set with its plugin, break the Login↔Profile cycle by movingcreateUserProfileto the command level.LOG(2008) and the file logger (header 31.08.2009) date from this rewrite. - 2009–2011 — command surface, DS housekeeping. The commands report documents the set
EquinoxConsolestill exposes; the jar-files how-to describes the core-JAR workflow that bundle updates superseded.650a48c4f(2011-09-02) setBundle-ActivationPolicy: lazyfor all DS bundles, still in every kernelbnd.bnd. - 2013–2015 — rename and configuration persistence.
062a51a1b(2014-03-15) renamedde.tud.kom.lifesocial.*toorg.lifesocial.*;1cdfab92a(2014-03-30) added framework-driven configuration storage and deleted the old activator code, soconfig.confandAbstractConfiguration/SECTIONbelong to this period, as does the STUN/NAT work (88b9632df) that introduced the recursivegetFramework(). - 2016 — Linux data directory to
$PWDfor NFS homes; back to$HOMEin the 2026 refactor. - 2020 — LibreSocial. Rename from LifeSocial (the commented-out
LifeSocialDataDir/"lifesocialdata" constants are the fossil), ECC 160-bit node identifiers replacing 1024-bit RSA, web front end, SkyEye metrics; the tuning file already carries the capacity/heterogeneity and social-cache switches. - 2025 — binary-first revival. JDK 1.7.0_80 + Eclipse Indigo as sanctioned toolchain, unlimited-strength
JCE policy jars, Docker branch; ~120 compile/start-up fixes, among them OSGi resource loading
(
getResourceAsStream→Bundle.getEntry), IP discovery on multi-loopback hosts andjava.rmi.server.hostnamefor the RMI tester. - 2026 — Gradle/Bndtools migration (merged
fa0f30ccc, 2026-09-13). Kernel changes: bnd files (2d9d29420), JavaSE-17 execution environments (6b651a1e1), OSGI-INF XML → annotations (189018957), OpenRewrite (3a9e918d0), launcher wrapper (6caddfdb9), SWT wrapper (f523b23dc),com.common.utilitiesrefactor (f8507fb12, reverted by9231d3daa, restored via35fa200e6; the refactored files withModified: 2026-05-18headers are what HEAD contains),./gradlew buildgreen (d9b96cd18), runtime fixes (d9ccc75b9,e49c67c60), container/console work (a7e004938,0967596b8,a94feb903,ce9b710a1), command injection restored (ba7b37a10, 2026-11-11). - Superseded or dead today: the Indigo/JDK 7 setup guide for the migrated tree (still valid for the
legacy branch);
libresocial.product's-Dosgi.requiredJavaVersion=1.7 -Xms96mVM arguments, whichbnd runnever reads; theMonitoringFPproduct extension; the commented-out DropboxbulletinURL; the core-JAR update procedure;ISystem's legacy methods (removed 2008); the compose data volume, disabled until the storage backend is fixed; and the self-recursiveLifeSocial.getFramework(), which the 2026 migration neither fixed nor removed.
Related publications
Core architecture and the OSGi decision
- A Peer-to-Peer based Framework for Large-Scale Social Networking Platforms (2008)
- Design and Implementation of a Service-oriented, Dynamic and Modular P2P-based Multimedia Online Community Platform using OSGi (2008)
- LifeSocial – Masterpraktikum: Entwurf und Implementierung neuer Plug-ins (2008)
- Updating the core LifeSocial library (How-To) (2009)
- LifeSocial Commands – Report (2009)
Platform papers documenting the runtime
- A Distributed Platform for Multimedia Communities (2008)
- LifeSocial.KOM: A P2P-based Platform for Secure Online Social Networks (2010)
- LifeSocial.KOM: A Secure and P2P-based Solution for Online Social Networks (2011)
- A P2P-Framework for Social Networks (2013)
- LibreSocial: A peer-to-peer framework for online social networks (2020)
- Peer-to-Peer Mechanisms for Fully Decentralized, Secure and Scalable Online Social Networks (2020)
- Systematic Evaluation of LibreSocial — A Peer-to-Peer Framework for Online Social Networks (2020)
Monitoring switches carried by the kernel configuration
- SkyEye.KOM: An Information Management Over-Overlay for Getting the Oracle View on Structured P2P Systems (2008)
- Monitoring and Management of Structured Peer-to-Peer Systems (2009)
- Monitoring and Management of Peer-to-Peer Systems (2010)
- SkyEye: A tree-based peer-to-peer monitoring approach (2017)
Configuration keys defined here, consumed further down
- Pastry: Scalable, decentralized object location and routing for large-scale peer-to-peer systems (2001)
- PAST: A large-scale, persistent peer-to-peer storage utility (2001)
- Sets, Lists and Trees: Distributed Data Structures on Distributed Hash Tables (2016)
- Caching Structures for Distributed Data Management in P2P-based Social Networks (2020)
- Capacity Management Protocol for a Structured P2P-based Online Social Network (2020)
Revival, build and operation