river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gtra...@apache.org
Subject svn commit: r1349505 - in /river/jtsk/skunk/surrogate: docs/SurrogateDeployment.txt src/org/apache/river/container/work/WorkManager.java
Date Tue, 12 Jun 2012 20:23:17 GMT
Author: gtrasuk
Date: Tue Jun 12 20:23:16 2012
New Revision: 1349505

URL: http://svn.apache.org/viewvc?rev=1349505&view=rev
Log:
Added a few "TODO" comments.

Added:
    river/jtsk/skunk/surrogate/docs/SurrogateDeployment.txt
      - copied, changed from r1342815, river/jtsk/skunk/surrogate/docs/Bootstrap.txt
Modified:
    river/jtsk/skunk/surrogate/src/org/apache/river/container/work/WorkManager.java

Copied: river/jtsk/skunk/surrogate/docs/SurrogateDeployment.txt (from r1342815, river/jtsk/skunk/surrogate/docs/Bootstrap.txt)
URL: http://svn.apache.org/viewvc/river/jtsk/skunk/surrogate/docs/SurrogateDeployment.txt?p2=river/jtsk/skunk/surrogate/docs/SurrogateDeployment.txt&p1=river/jtsk/skunk/surrogate/docs/Bootstrap.txt&r1=1342815&r2=1349505&rev=1349505&view=diff
==============================================================================
--- river/jtsk/skunk/surrogate/docs/Bootstrap.txt (original)
+++ river/jtsk/skunk/surrogate/docs/SurrogateDeployment.txt Tue Jun 12 20:23:16 2012
@@ -1,26 +1,20 @@
 
-The bootstrap process looks like this:
+Surrogate Deployment
+====================
 
-- The bootstrapper creates the overall container context object
-- Core configuration is read from the classpath at "o.a.r.c.core-config.xml".
-- Each component called out in the core configuration is instantiated and put
-into the context.  
-- The core config includes component callouts for the following:
-    - AnnotatedClassDeployer, which sets up dependency injection for the container
-    components.
-    - CommandLineArgumentParser, which reads the command line and sets appropriate
-    values into the context (mainly the profile directory).
-    - MBeanRegistrar, which takes note of any manageable components placed in 
-    the context, and registers them with the MBeanContainer.
-    - ShutdownListener, which acts as an MBean to allow shutdown of the 
-    container from a JMX console.
-    - FileUtilityImpl, which provides file services to other components.
-    - PropertiesFileReader, which reads all the '.properties' files in the 
-    profile directory, and puts them into the context under their file names.
-        - This facility allows components to simply declare a Properties object
-        and use the @Injected annotation to get their config files loaded.
-    - ProfileConfigReader, which reads the profile configuration and
-    sets up all the components in that config.
-        - The profile configuration is subject to more editing and customization
-        than the core config.
-    
+- So far as the container is concerned, a Surrogate is just another kind of
+application that is handled by a deployer.
+- The surrogate deployer sets up on an interface of some kind looking for 
+surrogates to deploy.  As per the surrogate over IP spec, this will involve
+setting up a multicast listener that responds to requests on the surrogate
+interface.
+- One thing to note - the surrogate deployer might be listening to a  different
+interface than the Jini workgroup is running on.  In the case of a non-TCP/IP
+surrogate, this is guaranteed to be the case.
+- For instance, let's say we have a PBX or asterisk implementation that wants
+to publish a Jini service by means of a surrogate.  The scenario is that the 
+surrogate talks to the PBX by means of UDP or simple TCP sockets.  If the PBX
+was unable to support a secured protocol, then a node might 
+have a connection on a private network to the PBX, but then might have a normal
+network connection for other clients of the PBX surrogate.  Since the surrogate 
+runs in the Java/Jini environment, it can use the full JERI security stack.
\ No newline at end of file

Modified: river/jtsk/skunk/surrogate/src/org/apache/river/container/work/WorkManager.java
URL: http://svn.apache.org/viewvc/river/jtsk/skunk/surrogate/src/org/apache/river/container/work/WorkManager.java?rev=1349505&r1=1349504&r2=1349505&view=diff
==============================================================================
--- river/jtsk/skunk/surrogate/src/org/apache/river/container/work/WorkManager.java (original)
+++ river/jtsk/skunk/surrogate/src/org/apache/river/container/work/WorkManager.java Tue Jun
12 20:23:16 2012
@@ -26,6 +26,9 @@ behalf.  Using a centralized workload ma
 control the scheduling of the workload and provide instrumentation on the 
 workload that might be useful for debugging or performance management.
 
+TODO: Need to have some way of grouping tasks, then killing off a task
+and all its subtasks (thread groups etc) for shutdown purposes.
+
  * @author trasukg
  */
 public interface WorkManager {



Mime
View raw message