[cap-talk] Graphs for real world distributed capabilities

John Carlson john.carlson3 at sbcglobal.net
Mon May 8 23:59:23 EDT 2006


Well, I haven't done work on capability graphs, but I've been working
on 3 dimensional graphs.  I have a network protocol for adding to the
graph and manipulating the graph through HTTP, so that you can have
a shared session with whatever is generating the graph.  I can send you
the code, if you like.  I don't have any persistence yet. It's  
programmed in JOGL.

It would be really cool if we could add capabilities to this, such  
that people
could only see certain parts of the graph.

I also have some 2D graph drawing tools that are similar, but a little
farther along in terms of labelling, nesting, and saving stuff.   The  
3D stuff
is the only stuff that is multiuser.

Let me know whether you want the code and your desired distribution
format.

John
On May 8, 2006, at 3:18 PM, Monty Zukowski wrote:

> So, I've got a new job and I'm trying to use capability security  
> discipline as
> we're architecting our Java servers (which run programs that do data
> transformation).  The idea right now is to try to follow the  
> guidelines in
> the Joe-E draft paper, and adopt the Joe-E tool once it is ready.
>
> We also need to worry about concurrency and distributed  
> programming.  Is
> anyone using the E-lib from Java?  I'd love to hear about real world
> performance issues, programming complexity, etc.  I realize that Joe-E
> intends to use it too, but we need to start programming already.
>
> Also, has anyone done any practical work on visualizing capability  
> graphs?
> I've been diagramming the objects representing the different types  
> of users
> we have and what they are allowed to do, and the objects that they can
> manipulate.  I noticed I needed to distinguish between object  
> creation and
> holding and passing of references.  Once I had about 20 objects in  
> there it
> wasn't quite as cute as, say, the Granovetter Diagram, although it  
> wouldn't
> be so bad if I broke it into subgraphs with just one page or graph  
> per class.
>
> Thanks,
>
> Monty
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk



More information about the cap-talk mailing list