Re: MRFC: Midgard site startup and configuration.
Torben Nehmer <[email protected]>
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again. - --Piotras wrote on 2006-02-07 10:20: > I am not any component developer but: Two sites I initilized without M-T are > not working anymore and frankly speaking I have no time or will to debug what > happened. However M-T is slow I vote for M-T. Reason is very simple. I know > that M-T based sites are going to work as expected. You think so, ok. I have nearly a dozen of examples where current M-T broke more things, than it fixed. It is purely a matter of perspective. We need a site management system, but not something like current M-T. > $some_midcom_object->root is much more readable than arrays' hell. > > [...] > > $some_midcom_site->port > $some_midcom_site->prefix > $some_midcom_site->whatever > > Is *much* more readable than another set of huge set of arrays. Leading to a table which needs to be extended with each and every configuration option I add to MidCOM. Right now, we already have literally dozens of such options (around 50 I guess) part of which are system-wide, part of it site-specific. Some options are even complex types, not simple ports or prefixes. Using a DB table is no real option here as it lacks flexibility. See my other mail for a better solution. Live long and Prosper! Torben Nehmer - -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:[email protected] PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD6HY+JPh4Kn6d5FYRAmCYAJ9+c7cmXPiCsyuN/TS+Qp6x3D6o6QCfeKs0 7QJrJi5zeXAA1piDvi1fJPE= =R5hd -----END PGP SIGNATURE-----