fehlerhafter Prototyp
SQL-Injections fehlen


BlooGee - Nr. 2
BlooGee - Nr. 3
BlooGee - Nr. 4
BlooGee - Nr. 5


README.txt - 13.05.2006, 11:51:57 - Page 1


What is BIooGee?

Initially, Bloo Gee was developed as a proof-of-concept work for a simple object model concerning microcontent. Main target is to provide an instrument to establish semantic networks, based an communications between webservers. BlooGee is (for now) a kind of add-on for weblogs and content management systems. It works on any structured content which can be described by a simple model identifyer, short description (or headline) and extended description (the main content). In this sense, almost any table with text data may be used by BlooGee. It is not intended as a replacement for existing systems, but as add-on for common blog Systems to establish communcation based an semantics between different weblogs.



How does BlooGee work?

In this first version, BIooGee simply provides a kind of desktop Interface to exsiting blog content as well as a command Shell to access (not only) Server functionality. There are some nice features like in-place editing, a Jot of AJAX-stuff and some basic tools to test and establish communications between different BlooGees. It basically supports a "site to site" protocol, based an simple HTTP requests. Concerning the content, BlooGee adds a special property to Single items: relations between micro content objects. In this sense, BlooGee provides search capabilities which are no longer based an keywords, but an semantics. If a search is done, it still starts with a keyword (and only one single keyword), but then focuses an (user provided) relations between items - and different sites.



BlooGee core functions

Basically BlooGee adds an abstraction layer for existing content. This layer is strictly embedded into a security layer which controls access to its core command Set. BlooGee supports unlimited users, user rights and command rights are expressed as simple numbers: if the command "level" is less or egaul than the user "level", the command is executed. In this sense, the BlooGee security model may easily be extended or used for own development. And - of course - own commands may be implemented.



Communication between BlooGee Servers

The BlooGee prototoll is inspired by existing peer-to-peer networks. Each time a request is made, lists of known other Servers are exchanged between Servers. And - of course - search requests are exchanged too. If a site is unreachable (but still up), a semantic network of BlooGees may fetch the content.



What is BIooGee made of?

BlooGee consists of a Set of PHP pages, a System database and a (individual configurable) main content database. Since BlooGee integrates ADODB, it is quite flexible regarding its environment. The surface is based an Scriptaculous and Prototype libraries. For coming versions, PEAR classes will be integrated for generating HTML pages.



Extensibility

BlooGee provides some simple APIs so it may be easily extended to own needs. Basically it needs an appropiate adaptor for its main content database. Since it is written strictly in the MVC model, BlooGee may easyly be extended with own Controllers to set up special functions.



Command Shell - VT-100 ;-)

Originally written as a debugger, the Command Shell provides terminal like access to BlooGee. It is like "tefneting weblogs" and has some interesting features for accessing content and BlooGees System database as well. Using the command shell, a simple webserver may be used like a "HTTP machine" to construct headers, monitor BlooGee activities, fetch and inspect remote sites, filter links from remote sites ...



How to use BIooGee

BlooGee may live in any subdir an the webserver. If configured properly, it provides a nice "blog desktop" with drag 'n drop capabilities, in place editing, user Jogin and a Page menu. If the command Shell is opened, it provides access to Server functions es described. To take full advantage of BlooGee, a change in the model of the content is required: Single items haue to be "tagged" with keywords and/or the URLs (permalinks) of related items. The more relatives, the more effective the semantic network. And the less the need of "keyword matches" for successful searches...



About this version

This is the first Version of BlooGee - still below 0.1 ;-) - which has the following capabilities:
- a full security layer, supporting an

- abstract layer of basic datbase commands.
- a full featured command Shell to access the
- basic Set of Server-to-Server prototoll functions; and
- an AJAX based desktop for blog-style display.
- Integration of ADODB.
- A widely open architecture for extensions and third Party plugins.




README.txt - 13.05.2006, 11:51:57 - Page 2

Note: this first version will preferably work an MySQL and Apache. Although a basic different between System tabies and content table is made, both (in this initial version) will haue to reside in the same db. Server protocol is limited to basics since there is still a problem with "exploding" requests so the appropiate code paus are more or less "symbolic". This will be fixed in the next version, which also will provide some more database adaptors for common Weblog/CM Systems (in O.OOf (at this time, there are adaptors for MovableType, Postnuke and Serendipidity).



TODO (for upcoming versions)

- establish real messaging and search capabilities between BlooGees.
- handle requests in System db by scripts
- export selections and results to tiddlers (TiddlyWiki friends - smile!!)
- and fix a Jot of bugs ;-))



PLEASE:
Read MCOM.txt and DEVNOTES.txt before installing BlooGee. USE AT OWN RISK, NO WARRANTIES. And: BACKUP YOUR DATA BEFORE INSTALLION!
XlwwwlREADME.fxt-File date: 13.05.2006-File time 11:34:01
X I wwwIREADME. txt - File date: 13.05.2006 - File time: 11:34:01



Keywords:
AJAX, Web 2.0, WEB 2.0, BlooGee, Markus Koch, Markus C. Koch
(siehe Koch in der Literaturliste Weblogs/Wikipedia und PHP-Nuke/Wikipedia)