After nearly two years of hosting with SourceForge.net, the Resourcerver Project has permanently moved to BerliOS.de. This move was for many reasons, to include the hosts' suitability for the project's audience, and it shouldn't be taken as an expression of negative opinions of SourceForge.net, professional or otherwise. The Resourcerver Project is grateful for all of the support and resources provided by SourceForge.net in the past. Please visit the new project page at http://rservr.berlios.de/. Thank you for your new or continued interest in my work.
Kevin P. Barry
Current Resourcerver source code statistics as of December 20th, 2008 (rservr-core-beta.14):
FILES: 331
LINES: 53072 (all)
RELEVANT: 30517 (non-blank/non-comment)
SIZE: 2.4M total
LONGEST 8: (by total lines)
1: 1639 libs/server/api-server.cpp
2: 1538 libs/server/client-list.cpp
3: 1434 programs/clients/rsv-forward/connect.cpp
4: 1429 libs/client/api-message-queue.cpp
5: 1329 programs/clients/rsv-forward/listen.cpp
6: 902 libs/proto/proto-resource/proto-resource-client.cpp
7: 875 lang/us-english/server.c
8: 837 libs/client/api-command-queue.cpp... read more
Resourcerver is a *nix framework for building modular applications. Resourcerver provides a structure to build a role-based system of discretely-purposed programs to form a dynamic application. This is done using a daemonized local-machine server which binds the system together, regulates its structure, and facilitates/controls communication between the application's components.
Resourcerver has been in the making for around a year and a half now. The first release was about a year after my first conceptualization because of the sheer complexity caused by the number of independent components. This beta release is a huge step forward for the Resourcerver project and it comes with a few changes in direction.... read more
Current Resourcerver source code statistics as of October 26th, 2008 (rservr-core-alpha.8):
FILES: 310
LINES: 48324 (all)
RELEVANT: 27506 (non-blank/non-comment)
SIZE: 2.3M total
LONGEST 8: (by total lines)
1: 1820 programs/clients/rsv-forward/socket-table.cpp
2: 1756 libs/server/client-list.cpp
3: 1145 libs/client/api-message-queue.cpp
4: 1099 libs/server/api-server.cpp
5: 896 libs/proto/proto-resource/proto-resource-client.cpp
6: 800 lang/us-english/server.c
7: 734 libs/client/api-command-queue.cpp
8: 701 libs/proto/proto-common/proto-common.cpp... read more
The current release of Resourcerver is alpha.6, which corrects a critical build error that occurred when compiling with certain GCC 3.* versions. This fatal error caused a message along the lines of "braces around scalar initializer for `const char* const*'". The error is caused by GCC's inability to initialize nested anonymous structures and unions with the respective compiler versions.... read more
Resourcerver is a system of *nix ("Unix®-like operating systems" such as Linux and FreeBSD) programs and libraries used to facilitate inter-process communication (IPC) for large, multi-process applications. In short, Resourcerver is intended to help developers create large applications using several smaller, special-purpose programs.
After months of work and incidental project maintenance, Resourcerver has a working example application to help demonstrate its capabilities and implementation. Other examples in various areas of implementation will follow, though I don't have a timeline established at this time.... read more
Resourcerver is a system of *nix ("Unix®-like operating systems" such as Linux and FreeBSD) programs and libraries used to facilitate inter-process communication (IPC) for large, multi-process applications. In short, Resourcerver is intended to help developers create large applications using several smaller, special-purpose programs.
Applications built around Resourcerver will generally be comprised of discrete processes based on specific functionality. Ideally, an application will have separate processes to manage data retrieval, data processing, network connections, and user control over the application. Resourcerver enforces several strictly-defined process types that the derived application categorizes its own processes by. All of the application's processes are connected via a Resourcerver server at its core. The server process is the head of the application itself and enforces a strict set of security policies for both processes communicating with each other and for processes controlling the operation of the server.... read more