Okay, here is what I gather as far as a roadmap/todo list, feel free to
bring up changes/ideas as I am just throwing it together based on our
discussions to date:
Version 0.0.0
-------------
Current -> Includes basic (not necessarily compiling) code framework and
CVS module
Version 0.0.1
-------------
Bryce: First Config class implementation (basic)
Nate: Network class implementation (tested with thread-test module by
Dave)
Dave: First TokenCollection class implementation (basic), using STL map
After version 0.0.1 is in CVS, we should be able to use thread-test to
do some initial analysis of the thread design etc. I am guessing this
is something we will all want to be involved in. I have not included
'assignments' of people->task for future revisions, as we can deal with
that in the future, spreading out the work to where each of us feels
most comfortable/has time etc...
Version 0.0.2
-------------
Config class implementation (full)
TokenCollection class implementation (full)
Basic TokenHandler implementation
Basic PAM (client side) module, connects to server, prints recieved
token
Version 0.0.3
-------------
Extend client PAM, reads Config, connects to server, puts token in /proc
Basic client kernel module, creates /proc file for client PAM
Version 0.0.4
-------------
Full TokenHandler implementation
Full client PAM
At this point then, we should have a snfsd server process that can read
its config, listen/grant token requests, kick off threads (that do
nothing for now). We should also have a client PAM module that can read
its config, request and recieve tokens, and a client Kernel module that
creates the appropriate /proc area. We can then re-evaluate where we
are, review design and other decisions, and determine the best way to go
forward again.
Let me know what you think... this should give us plenty to do for the
time being. I am going to get to work on the NetworkServer class so we
can start doing some testing with threads etc..
Nate
|
