A task management system. At least this was the initial idea. Basically this it the base code for the taskrambler framework.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Georg Hopp 2446a2f293 add small example on rbtree insert, just to see what I have to care about when implementing this 12 years ago
assets add latest stuff from parent project yabrog. Essentially some request variable handling and authentication interface with ldap implementation. Additionally add docBlocks to all C source and header files and make a real copyright sign from the (C). 14 years ago
certs initial fork from server project 14 years ago
docs add small example on rbtree insert, just to see what I have to care about when implementing this 12 years ago
include simplified the quick fit interface 12 years ago
m4 change build system to accept CFLAGS 12 years ago
src add first own binary tree testcode. Not ballanced right now. 12 years ago
tests fix some warnings 12 years ago
.doxygen initial fork from server project 14 years ago
.gitignore now ignore log tsr files under tests 12 years ago
AUTHORS initial fork from server project 14 years ago
COPYING initial fork from server project 14 years ago
ChangeLog initial fork from server project 14 years ago
Makefile.am huge changes in build system. Moved a lot of stuff to separate archives, not finished right now. Additionally add some support for coverage reports. Next step after build restructuring is to write tests. 14 years ago
Makefile.am.coverage small changes in build system 13 years ago
NEWS initial fork from server project 14 years ago
README initial fork from server project 14 years ago
TODO probably fixed problem in main look under load. This still has to be tested. 12 years ago
bootstrap initial fork from server project 14 years ago
configure.ac add build dir as macro definition to daemonze.c thus been able to chdir there so that all assets would be found. 12 years ago

README

Actually this is some kind of server toolkit, also containing
a class and interface toolkit for C.
I use a gcc preprocessor extension to use empty variadoc
argument lists so actually this is gcc only code.

This should become a server that has a dynamic time-sliced part
that updates an internal state all the time.
Clients might connect as they want and get some information
from the server.
The server should scale in two manners.
New instances should be able to handle connection and get
updates about the computed state.
Additionally new instances might hold their own state which
all other instances might update.

In a first run the state might be something simple as a
matrix where every field hold a unique value. e.g.

-------------
|1|4|a|j|k|9|
-------------
|1|4|a|j|k|9|
-------------
|1|4|a|j|k|9|
-------------
|1|4|a|j|k|9|
-------------

suggestion for timing: sigsuspend