Subject | RE: [firebird-support] Embedded again |
---|---|
Author | Chad Z. Hower |
Post date | 2005-07-01T16:25:06Z |
:: With Vulcan you'll need at least two dlls currently called
:: firebird.dll
:: and engine8.dll. If you want remote access, you'll need remote.dll.
I can live with 2. :)
:: You'll also need a text file called vulcan.conf. If those
:: files are in
:: the same directory with your binary image, you don't need
:: environmental
:: variables or registry entries.
That will work. :)
:: There are some technical problems - events don't work, the
:: services api
:: has been sketched but not even seriously designed, etc. And
:: of course
:: there are pragmatic issues - like it won't be called Vulcan, so what
:: will it be called ....
Ok - best guesstimate on ETA? :)
:: firebird.dll
:: and engine8.dll. If you want remote access, you'll need remote.dll.
I can live with 2. :)
:: You'll also need a text file called vulcan.conf. If those
:: files are in
:: the same directory with your binary image, you don't need
:: environmental
:: variables or registry entries.
That will work. :)
:: There are some technical problems - events don't work, the
:: services api
:: has been sketched but not even seriously designed, etc. And
:: of course
:: there are pragmatic issues - like it won't be called Vulcan, so what
:: will it be called ....
Ok - best guesstimate on ETA? :)