dc4db

DialogComponents
for
DataBases

Welcome to dc4db on sourceforge.net

dc4db brings dialogs and databases together ...


Environment(s):	pWS		dcWrap
	dcT for pWS	<-- dc structural data-->	dcT
	dcP for pWS	<-- dc plain data-->	dcP
		^ \| \| dc apps

Concept preface

To think about dialogs and databases today, there are very much possibilities to select environments to create communications and database usages.

About creating and run dialogs, the choices are

Operation systems environments, like Windows, KDE etc.
Runtime environments like JRE etc., to have more independence to the operating systems
Universal environments by protocols like HTTP etc., supported in nearly all operating systems
A lot of specialized environments, not mentioned here furthermore.

As more as an environment is specific, the possibilities for styling, interactions and processing are more extensive, but at the same time the universal commitment even becomes reduced.

To thrash out the possibilities today to implement dialogs with most universal commitments, a choice of internet technologies is the best, although sure not the most powerful way. But in so many much cases that may be enough.

That is the way dc4db goes.

In general, there are two types of data processed today. Structured data most feed in relational database systems, and plain data like text placed anywhere, but also in databases. To think about dialogs once more again, both types of data should be supported by a system wants to have a bit of universal approach.

To think about communications, to contact a client is easy because he most will have a web browser, of what type ever. That is a precondition dialog systems may exploit. The developers have to invest nothing themselves to enable the clients part of a communications path. Especially because the most web browsers have a focus to standards established worldwide, although not implemented always perfect in any way. But the staging to the future is promising.

dc4db is a playground in the fields running database and web servers at the servers side, and web browsers at the clients side. Like some products worldwide, it far away from being finished.

The modules of dc4db are published in different time intervals and consist of different layers. The own dc4db wrapper is not published today because it is only in an experimental state. As much more than a compensation, the cms phpWebsite is prefered from the author. Thats because the cms phpWebSite has its outstanding impressed modularity in design, supporting developers so easy to build own functionalities.

Implementations

The one part of dc4db to support plain data, is the dcP module implemented first in phpWebSite with the working title dcPublisher, version 0.1.x. A second part, to handle structured data, the dcT module, becomes soon being offered. The later cooperation of dcP and dcT perhaps may be a matter of some interests.

State: Dec 2005

dcPublisher homepage at: http://dcp.dc4db.net/

dc4db homepage at: http://dc4db.net/

200501.4-0.sfhome.hi
200512.4-0 sfhome.hi