Jim
Where can I find the Vulcan source ?

--- Firebird-Architect@yahoogroups.com wrote:

>
> There are 2 messages in this issue.
>
> Topics in this digest:
>
> 1. Re: Digest Number 916
> From: Bruce Bacheller
> <bruce_bacheller@...>
> 2. Vulcan Merge
> From: Jim Starkey
> <jas@...>
>
>
>

________________________________________________________________________

>

________________________________________________________________________

>
> Message: 1
> Date: Fri, 28 Jan 2005 19:41:54 -0800 (PST)
> From: Bruce Bacheller <bruce_bacheller@...>
> Subject: Re: Digest Number 916
>
> Jim, I am developing a RSS Feed for FirebirdConnect
> I
> can set it up so Vulcan can have posts to a Vulcan
> "Channel" which acts like a Discussion Forum. The
> Feed
> and links can viewed online or downloaded.
> If you are interested lets discuss some more. My
> delivery for 1.0 is Mid feb.
>
> --- Firebird-Architect@yahoogroups.com wrote:
>
> >
> > There is 1 message in this issue.
> >
> > Topics in this digest:
> >
> > 1. Re: SourceForge Lists
> > From: Milan Babuskov <milanb@...>
> >
> >
> >
>

________________________________________________________________________

> >
>

________________________________________________________________________

> >
> > Message: 1
> > Date: Fri, 28 Jan 2005 09:27:29 +0100
> > From: Milan Babuskov <milanb@...>
> > Subject: Re: SourceForge Lists
> >
> > Jim Starkey wrote:
> > > Something I considering setting up for Vulcan
> was
> > a web-based discussion
> > > forum with email notification. A web based
> > display has a number of
> > > clear advantages -- it shows the posts as a
> tree,
> > performs uniform
> > > formatting, supports attachments, lets a
> responder
> > see the full state of
> > > the thread before responding, and keeps a full
> > archive of threads. I
> > > don't know the downsides because I haven't
> > deployed it yet. It would
> > > probably take some iteration to get right, but
> for
> > the devel list, I
> > > think it would be a big step forward.
> >
> > The main drawback is that you have to be online to
> > read it. It creates problems
> > if you have dial-up connection, when you travel,
> > etc.
> >
> > > Any other thoughts?
> >
> > IMHO, The Best Thing (TM) to do would be to setup
> > both forum and mailing list,
> > something like wxWidgets project has done. They
> made
> > it available to read/post
> > to both the forum and mailing list (and a
> newsgroup
> > too, btw).
> >
> > Relevant URLs:
> >
> > http://www.wxwidgets.org
> > http://www.wxforum.org
> >
> > --
> > Milan Babuskov
> > http://fbexport.sourceforge.net
> > http://www.flamerobin.org
> >
> >
> >
> >
> >
>

________________________________________________________________________

> >
>

________________________________________________________________________

> >
> >
> >
> >
>

------------------------------------------------------------------------

> > Yahoo! Groups Links
> >
> > http://groups.yahoo.com/group/Firebird-Architect/
> >
> > Firebird-Architect-unsubscribe@yahoogroups.com
> >
> >
> >
>

------------------------------------------------------------------------

> >
> >
> >
> >
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
>
> http://promotions.yahoo.com/new_mail
>
>
>

________________________________________________________________________

>

________________________________________________________________________

>
> Message: 2
> Date: Sat, 29 Jan 2005 13:36:59 -0500
> From: Jim Starkey <jas@...>
> Subject: Vulcan Merge
>
> The strategy to merge Vulcan and Firebird 2.0 to
> form Firebird 3.0 will
> probably be gated by a single central question: Will
> Firebird 3.0 use
> the Vulcan provider architecture.
>
> Firebird 2.0 consists of two main pieces: A client
> library and a server
> executable (some platforms have an embedded engine
> packages as a plug
> replacement for the client library). The client
> library contains a
> Y-valve front-ending the remote interface. The
> server executable
> contains the server code, the Y-valve, and an
> engine.
>
> In the Vulcan provider architecture, the client
> library (Firebird.dll
> or libfirebird.so) contains only the Y-valve.
> During the database
> attach operation, the Y-valve, under control of a
> configuration files,
> tries to load provider modules from an ordered list
> until one is able to
> successfully attach the database. Vulcan currently
> has providers for
> the engine, the remote interface, and a gateway to
> legacy Firebird and
> Interbase. When the ODS is changed, Vulcan gets
> another engine
> provider, retaining the old shared libraries
> (buildable only from a CVS
> tag) for backwards compatibility. Finally, in
> Vulcan, the server is an
> executable linked to the same client library as
> ordinary client programs.
>
> The provider architecture has a number of
> advantages. One is the
> ability to perform rolling upgrades. In Firebird
> 2.0, there are two
> ways to provide access to databases with different
> ODSes. One is to
> have the single engine support a variety of ODSes.
> The other is for the
> user to balance two (or more) Firebird installs on
> the same system. For
> former is constraining on development, leading to
> unnecessarily complex
> code to straddle versions, while the latter shift
> the burden to the
> user. The Vulcan provider architecture, on the
> other hand, allows us to
> release a new engine version as a new provider,
> leaving the existing
> engine(s) in place, with a tweak of the core
> configuration file. This
>

=== message truncated ===




__________________________________
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250