Package net.i2p
Class I2PAppContext
java.lang.Object
net.i2p.I2PAppContext
- Direct Known Subclasses:
RouterContext
Provide a base scope for accessing singletons that I2P exposes. Rather than using the traditional singleton, where any component can access the component in question directly, all of those I2P related singletons are exposed through a particular I2PAppContext. This helps not only with understanding their use and the components I2P exposes, but it also allows multiple isolated environments to operate concurrently within the same JVM - particularly useful for stubbing out implementations of the rooted components and simulating the software's interaction between multiple instances.
As a simplification, there is also a global context - if some component needs access to one of the singletons but doesn't have its own context from which to root itself, it binds to the I2PAppContext's globalAppContext(), which is the first context that was created within the JVM, or a new one if no context existed already. This functionality is often used within the I2P core for logging - e.g.private static final Log _log = new Log(someClass.class);It is for this reason that applications that care about working with multiple contexts should build their own context as soon as possible (within the main(..)) so that any referenced components will latch on to that context instead of instantiating a new one. However, there are situations in which both can be relevant.
-
Field Summary
Modifier and TypeFieldDescriptionprotected Clock
protected boolean
protected static I2PAppContext
the context that components without explicit root are boundprotected KeyRing
protected boolean
protected final I2PProperties
protected SessionKeyManager
protected boolean
-
Constructor Summary
ModifierConstructorDescriptionCreate a brand new context.protected
I2PAppContext
(boolean doInit, Properties envProps) Create a brand new context.I2PAppContext
(Properties envProps) Create a brand new context. -
Method Summary
Modifier and TypeMethodDescriptionvoid
Add a callback, which will fire upon changes in the property given in the specific callback.void
addShutdownTask
(Runnable task) WARNING - Shutdown tasks are not executed in an I2PAppContext.aes()
Ok, I'll admit it.As of 0.9.30, returns non-null in I2PAppContext, null in RouterContext.clock()
The context's synchronized clock, which is kept context specific only to enable simulators to play with clock skew among different instances.void
don't rely on deleteOnExit()dsa()
Our DSA engine (see HMAC and SHA above)This is the ElGamal engine used within this context.Where applications may store data.This is the installation dir, often referred to as $I2P.boolean
getBooleanProperty
(String propName) Default falseboolean
getBooleanPropertyDefaultTrue
(String propName) The base dir for config files.static I2PAppContext
Pull the default context, WITHOUT creating a new one.long
How long this router was down before it started, or 0 if unknown.static I2PAppContext
Pull the default context, creating a new one if necessary, else using the first one created.This is the library dir, which is usually $I2P/lib.Where the router keeps its log directory.Where router.ping goes.Access the configuration attributes of this context, listing the properties provided during the context construction, as well as the ones included in System.getProperties.getProperty
(String propName) Access the configuration attributes of this context, using properties provided during the context construction, or falling back on System.getProperty if no properties were provided during construction (or the specified prop wasn't included).boolean
getProperty
(String propName, boolean defaultVal) Return a boolean with a boolean defaultint
getProperty
(String propName, int defaultVal) Return an int with an int defaultlong
getProperty
(String propName, long defaultVal) Return a long with a long defaultgetProperty
(String propName, String defaultValue) Access the configuration attributes of this context, using properties provided during the context construction, or falling back on System.getProperty if no properties were provided during construction (or the specified prop wasn't included).Access the configuration attributes of this context, listing the properties provided during the context construction, as well as the ones included in System.getProperties.Where the router keeps its files.Where anybody may store temporary data.boolean
Is the wrapper present?hmac256()
Un-deprecated in 0.9.38protected void
protected void
protected void
Use this to connect to the router in the same JVM.boolean
Use this instead of context instanceof RouterContextComponent to generate ElGamal, DSA, and Session keys.keyRing()
Basic hash mapQuery the log manager for this context, which may in turn have its own set of configuration settings (loaded from the context's properties).Pull up the naming service used in this context.Basic mapping from service names to portsrandom()
[insert snarky comment here]void
removeShutdownTask
(Runnable task) Determine how much do we want to mess with the keys to turn them into something we can route.The session key manager which coordinates the sessionKey / sessionTag data.protected static boolean
Sets the default context, unless there is one already.void
setLogManager
(LogManager logManager) Overwrites the LogManager instance to be used by the router.sha()
Our SHA256 instance (see the hmac discussion for why its context specific)Deprecated.in 0.9.20, use simpleTimer2()Deprecated.use SimpleTimer2Use instead of SimpleTimer2.getInstance()The statistics component with which we can track various events over time.
-
Field Details
-
_globalAppContext
the context that components without explicit root are bound -
_overrideProps
-
_sessionKeyManager
-
_clock
-
_keyRing
-
_sessionKeyManagerInitialized
protected volatile boolean _sessionKeyManagerInitialized -
_clockInitialized
protected volatile boolean _clockInitialized -
_keyRingInitialized
protected volatile boolean _keyRingInitialized -
_shutdownTasks
-
-
Constructor Details
-
I2PAppContext
public I2PAppContext()Create a brand new context. WARNING: In almost all cases, you should use getGlobalContext() instead, to avoid creating additional contexts, which may spawn numerous additional resources and threads, and may be the cause of logging problems or hard-to-isolate bugs. -
I2PAppContext
Create a brand new context. WARNING: In almost all cases, you should use getGlobalContext() instead, to avoid creating additional contexts, which may spawn numerous additional resources and threads, and may be the cause of logging problems or hard-to-isolate bugs. -
I2PAppContext
Create a brand new context. WARNING: In almost all cases, you should use getGlobalContext() instead, to avoid creating additional contexts, which may spawn numerous additional resources and threads, and may be the cause of logging problems or hard-to-isolate bugs. NOT a public API, for use by RouterContext only, NOT for external use.- Parameters:
doInit
- should this context be used as the global one (if necessary)? Will only apply if there is no global context now.- Since:
- protected since 0.9.33, NOT for external use
-
-
Method Details
-
getGlobalContext
Pull the default context, creating a new one if necessary, else using the first one created. Warning - do not save the returned value, or the value of any methods below, in a static field, or you will get the old context if a new router is started in the same JVM after the first is shut down, e.g. on Android. -
setGlobalContext
Sets the default context, unless there is one already. NOT a public API, for use by RouterContext only, NOT for external use.- Parameters:
ctx
- context constructed with doInit = false- Returns:
- success (false if previously set)
- Since:
- 0.9.33
-
getCurrentContext
Pull the default context, WITHOUT creating a new one. Use this in static methods used early in router initialization, where creating a context messes things up.- Returns:
- context or null
- Since:
- 0.8.2
-
getBaseDir
This is the installation dir, often referred to as $I2P. Applilcations should consider this directory read-only and never attempt to write to it. It may actually be read-only on a multi-user installation. The config files in this directory are templates for user installations and should not be accessed by applications. The only thing that may be useful in here is the lib/ dir containing the .jars.- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getConfigDir
The base dir for config files. Applications may use this to access router configuration files if necessary. Usually ~/.i2p on Linux and %APPDIR%\I2P on Windows. In installations originally installed with 0.7.5 or earlier, and in "portable" installations, this will be the same as the base dir.- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getRouterDir
Where the router keeps its files. Applications should not use this. The same as the config dir for now.- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getPIDDir
Where router.ping goes. Applications should not use this. The same as the router dir by default as of 0.8.12 Was the same as the system temp dir prior to that. Which was a problem for multi-user installations.- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getLogDir
Where the router keeps its log directory. Applications should not use this. The same as the config dir for now. (i.e. ~/.i2p, NOT ~/.i2p/logs)- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getAppDir
Where applications may store data. The same as the config dir for now, but may change in the future. Apps should be careful not to overwrite router files.- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getTempDir
Where anybody may store temporary data. This is a directory created in the system temp dir on the first call in this context, and is deleted on JVM exit. Applications should create their own directory inside this directory to avoid collisions with other apps.- Returns:
- dir constant for the life of the context
- Since:
- 0.7.6
-
getLibDir
This is the library dir, which is usually $I2P/lib. It contains all the jars (i.e. the classpath). Most applications will not need this, and must treat this directory as read-only.- Returns:
- dir constant for the life of the context
- Since:
- 0.9.52
-
deleteTempDir
public void deleteTempDir()don't rely on deleteOnExit() -
getProperty
Access the configuration attributes of this context, using properties provided during the context construction, or falling back on System.getProperty if no properties were provided during construction (or the specified prop wasn't included). -
getProperty
Access the configuration attributes of this context, using properties provided during the context construction, or falling back on System.getProperty if no properties were provided during construction (or the specified prop wasn't included). -
getProperty
Return an int with an int default -
getProperty
Return a long with a long default- Since:
- 0.9.4
-
getProperty
Return a boolean with a boolean default- Since:
- 0.7.12
-
getBooleanProperty
Default false- Since:
- 0.7.12
-
getBooleanPropertyDefaultTrue
- Since:
- 0.7.12
-
getPropertyNames
Access the configuration attributes of this context, listing the properties provided during the context construction, as well as the ones included in System.getProperties. WARNING - not overridden in RouterContext, doesn't contain router config settings, use getProperties() instead.- Returns:
- set of Strings containing the names of defined system properties
-
getProperties
Access the configuration attributes of this context, listing the properties provided during the context construction, as well as the ones included in System.getProperties.- Returns:
- new Properties with system and context properties
- Since:
- 0.8.4
-
addPropertyCallback
Add a callback, which will fire upon changes in the property given in the specific callback. Unimplemented in I2PAppContext: this only makes sense in a router context.- Parameters:
callback
- The implementation of the callback.
-
statManager
The statistics component with which we can track various events over time. -
sessionKeyManager
The session key manager which coordinates the sessionKey / sessionTag data. This component allows transparent operation of the ElGamal/AES+SessionTag algorithm, and contains all of the session tags for one particular application. This is deprecated for client use, it should be used only by the router as its own key manager. Not that clients are doing end-to-end crypto anyway. For client crypto within the router, use RouterContext.clientManager.getClientSessionKeyManager(dest) As of 0.9.15, this returns a dummy SessionKeyManager in I2PAppContext. The dummy SKM does NOT handle session tags. Overridden in RouterContext to return the full TransientSessionKeyManager. -
initializeSessionKeyManager
protected void initializeSessionKeyManager() -
namingService
Pull up the naming service used in this context. The naming service itself works by querying the context's properties, so those props should be specified to customize the naming service exposed. -
elGamalEngine
This is the ElGamal engine used within this context. While it doesn't really have anything substantial that is context specific (the algorithm just does the algorithm), it does transparently use the context for logging its performance and activity. In addition, the engine can be swapped with the context's properties (though only someone really crazy should mess with it ;) -
aes
Ok, I'll admit it. there is no good reason for having a context specific AES engine. We dont really keep stats on it, since its just too fast to matter. Though for the crazy people out there, we do expose a way to disable it. -
logManager
Query the log manager for this context, which may in turn have its own set of configuration settings (loaded from the context's properties). Each context's logManager keeps its own isolated set of Log instances with their own log levels, output locations, and rotation configuration. -
setLogManager
Overwrites the LogManager instance to be used by the router. This should only be called after the Router is instantiated but before it is started. Calling this at any other time can have unpredictable side effects.- Since:
- 0.9.41
-
hmac256
Un-deprecated in 0.9.38 -
sha
Our SHA256 instance (see the hmac discussion for why its context specific) -
dsa
Our DSA engine (see HMAC and SHA above) -
keyGenerator
Component to generate ElGamal, DSA, and Session keys. For why it is in the appContext, see the DSA, HMAC, and SHA comments above. -
clock
The context's synchronized clock, which is kept context specific only to enable simulators to play with clock skew among different instances. -
initializeClock
protected void initializeClock() -
routingKeyGenerator
Determine how much do we want to mess with the keys to turn them into something we can route. This is context specific because we may want to test out how things react when peers don't agree on how to skew. As of 0.9.16, returns null in I2PAppContext. You must be in RouterContext to get a generator.- Returns:
- null always
-
keyRing
Basic hash map -
initializeKeyRing
protected void initializeKeyRing() -
random
[insert snarky comment here] -
addShutdownTask
WARNING - Shutdown tasks are not executed in an I2PAppContext. You must be in a RouterContext for the tasks to be executed at shutdown. This method moved from Router in 0.7.1 so that clients may use it without depending on router.jar.- Since:
- 0.7.1
-
removeShutdownTask
- Since:
- 0.9.53
-
getShutdownTasks
- Returns:
- an unmodifiable Set
- Since:
- 0.7.1
-
isRouterContext
public boolean isRouterContext()Use this instead of context instanceof RouterContext- Since:
- 0.7.9
-
internalClientManager
Use this to connect to the router in the same JVM.- Returns:
- always null in I2PAppContext, the client manager if in RouterContext
- Since:
- 0.8.3
-
hasWrapper
public boolean hasWrapper()Is the wrapper present?- Since:
- 0.8.8
-
portMapper
Basic mapping from service names to ports- Since:
- 0.8.12
-
simpleScheduler
Deprecated.in 0.9.20, use simpleTimer2()Use instead of SimpleScheduler.getInstance()- Since:
- 0.9 to replace static instance in the class
-
simpleTimer
Deprecated.use SimpleTimer2Use instead of SimpleTimer.getInstance()- Since:
- 0.9 to replace static instance in the class
-
simpleTimer2
Use instead of SimpleTimer2.getInstance()- Since:
- 0.9 to replace static instance in the class
-
clientAppManager
As of 0.9.30, returns non-null in I2PAppContext, null in RouterContext. Prior to that, returned null always. Overridden in RouterContext to return the RouterAppManager.- Returns:
- As of 0.9.30, returns non-null in I2PAppContext, null in RouterContext
- Since:
- 0.9.11, in RouterContext since 0.9.4
-
getEstimatedDowntime
public long getEstimatedDowntime()How long this router was down before it started, or 0 if unknown. This may be used for a determination of whether to regenerate keys, for example. We use the timestamp of the previous ping file left behind on crash, as set by isOnlyRouterRunning(), if present. Otherwise, the last STOPPED entry in the event log. May take a while to run the first time, if it has to go through the event log. Once called, the result is cached.- Returns:
- 0 always in app context
- Since:
- 0.9.47
-