> > Then we`ll do a start with Broken Shinai.
>
> Ok. The Broken Shinai handles its database connection via
> ODBC but will still probably work only with MySQL, as some
> SQL used in Midgard is code specific to that database. I'm
> not sure how much work it would be to hunt down all those
> parts of Midgard and change them to more generic ones.
But the inital odbc support might make it easier, to do the
full odbc port for Win32. That`s why I choosed Borken Shinai.
Even if it`s slower, it might help to find a way to do the
Win32 port.
> This all will change with Midgard 2 which has been pretty
> much designed with ODBC and multiple databases in mind.
> > How about Midgard 2.0 ? Will it be for PHP3 or PHP4 ?
> Midgard 2 will probably use PHP4, as that should be out
> before we get Midgard 2 ready.
Using PHP4 will make Midgard easier to implement in Win32.
It has better Win32 support and will be available as module
finally, so no cgi fiddling anymore.
Another one: I saw that the midgard manual is quite empty.
If needed, i could at least help in writing the installation
part for current 1.2.4 release. I installed Midgard 1.2.4
with Apache 1.3.9, mod_ssl 2.4.6, OpenSSL 0.9.4 and MySQL
3.22.27 and had no problems doing so. I could write a step-by-step
guide for beginners. Since I`m coming from the NT world, this
could be quite useful for beginners starting with Midgard.
Tell me, if i can help you in that way. Since I like Midgard`s
way of serving sites, i would like to give something back in turn.
Daniel
______________________________________________________________________
The OpenSA Project http://www.opensa.de/
Project Information [EMAIL PROTECTED]
Daniel Reichenbach [EMAIL PROTECTED]
______________________________________________________________________
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
