ghopp
/
taskrambler
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
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.
126 Commits
8 Branches
10 Tags
3.6 MiB
 
 
 
 
 
 
Tree: 7ebd5a6a00
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7ebd5a6a00'
${ noResults }
Georg Hopp 7ebd5a6a00
add subdir-objects to each Makefile.am 		12 years ago
assets try to use memory mapped io for asset access, but this one leaks like a rotten barge 12 years ago
certs initial fork from server project 14 years ago
config add suppport for file extension based mime type detection. 12 years ago
docs added some thoughts about socket states while reading and writing. This is not handled very well right now in my code which result in connections to be closed to early. 12 years ago
include a fix in size of asset names and change in logging 12 years ago
m4 change build system to accept CFLAGS 12 years ago
src add subdir-objects to each Makefile.am 12 years ago
tests don't use non automake makefiles under tests anymore 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
README.md first README.md 13 years ago
TODO most likely found a bug in the glibc tdelete implementation...don't have the mood of building a simple testcase for reporting. Maybe I do when I have implemented my own trees. 12 years ago
bootstrap initial fork from server project 14 years ago
configure.ac version bump 12 years ago

README.md

libHttpServer

This is a partly finished implementation of HTTP/1.1. It is especially intendet to write C only REST server, well, at least thats the idea.

INSTALLATION

Currently there is no finished installation process. Further more, packages are required for building this thing, that in fact are only requered for the testing part.

BUILD REQUIREMENTS

You need the following to build this thing.

  • A GNU Autobuild (autoconf, automake, etc.) installation.
  • GCC as well as binutils.
  • lcov (this dependency has to change as it is really only related to testing.

BUILDING

Call ./bootstrap and then run ./configure. After that run make. After that you will hopefully find a binary called taskrambler under src/. This is a test application for the library. It's name comes from the first intention what i would like to do with it. Some kind of task management system.

INSTALLING

Currently i am not sure if this thing will install correctly. You might try at your own risk. Anyway, no install should be needed to test this thing.

USAGE

RUNNING

Simply start the executable src/taskrambler after successfull build. Currently this will stay in the foreground and does logging via syslog.

PORT

The server will listen on port 11212 for HTTP requests and on port 11213 for SSL requerst.

You can use telnet or simply start a browser and connect on localhost:11212.

This should show up a very simplistic page. It should eneable you to start a session, get values from the server or login.

LOGIN

You can't use the login without changing the code. It implemented using ldap and currently not configurable. You have to change the configuration in the code and compile again.

TESTING

This comes with an incomplete unit test suite. You can use make test to build and run the existent tests.

REQUIREMENTS

Currently, you need valgrind to build the tests, because some memory checking is done by the way.

CONTRIBUTION

I would really like to see some people possibly interested in this stuff. I think it contains some really interesting ideas.

Well, sadly i have to say that this is a spare time project. Documentation is sparse and Tests too.

If you like to contribute anyway, make a fork, do you changes and generate a pull request.

I will look at these as soon as possible.