[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: object change notification
- To: email@example.com
- Subject: Re: object change notification
- From: Falko Braeutigam <firstname.lastname@example.org>
- Date: Sun, 18 Jun 2000 14:45:21 +0200
- In-Reply-To: <email@example.com>
- Organization: SMB
- References: <firstname.lastname@example.org>
On Thu, 15 Jun 2000, Davide Mora wrote:
> Hi Falko!
> > Wow, great! Do you have a link or something where we
> > may find more about this
> > project?
> you can take a look to http://perfekt.sourceforge.net,
> but there is not a lot, i'm sorry, we'll work on the
> web site later, when there will be a downloadable
> version (one-two months).
> also the screenshot it's very old, i'll make a new one
> in the next days, i'm finishing the relations
> > No, unfortunately there no such build-in
> > notification system. Let's make a
> > wish list for a notification API!
> i used notification api with commercial OODMBS in the
> past, expecially in the financial field, it's really
> useful: more speed with less "stress" for the whole
> many commercial databases have/had problems about this
> feature... not so used = not so tested i think.
> > That means I would prefer some kind of polling from
> > the client. This would make
> > things much easier to implement.
> yes. i agree, i'll try to develop something in the
> next weeks.
To be honest, I was expecting some more feedback from the group to such an
important questions of the ozone development. I cannot believe that nobody here
on the list knows other notification APIs (open or closed) or wants to see this
or that feature in a new ozone API.
Currently there are 176 subscribers in the list, which I feel is not that bad -
but only very few people seem to be willing or able to contribute their
knowledge and to dicuss things. I know, the development process of ozone is not
that transparent as it should be but I'm always trying to encourage you to ask
about things that are not that clear and to say your opinion. I'm afraid,
I'm doing something wrong.
Okay guys, first we should clarify our expectations. What do you expect from
ozone? (technical features, development process, mail list, homepage, whatever)
And second: What do you think goes wrong today?
The lack of documentation is a very bad thing. I will try to make some
diagrams next week.
Technically I'm I expecting ozone to be a tool that reflects the needs of real
world applications. But also a tool that provides advanced OODBMS features and
techniques: the result of an active community that represents the leading edge
of OODBMS development. Hey, why this shouldn't happen? We are 176 guys here.
Together we are representing todays OODBMS knowledge, I guess. So what are we
waiting for? A base architecture is there, an implementation to discuss about
is there, people are there... what's missing?
As all of you know, I'm dicussing the possibilities to make Infozone an Apache
XML project with Stefano Mazzocchi. During discussion I found that he is
also interested in an XML database (ozone/XML) and a general OODBMS (ozone).
Unfortunately I'm not sure if we as a group are ready to go in this direction.
People, I need your help! One thing is for sure, I'm not able to do the entire
ozone development by myself. So, if you are really interested in ozone, then
the time is here to jump in, share your knowledge and ideas, discuss things,
test new code, whatever.
Falko Braeutigam mailto:email@example.com
softwarebuero m&b (SMB) http://www.softwarebuero.de