Hello Emiliano,
you wrote:
>> find exact message). Actually, we'll need to have several such
>> wrappers: one for DB, one for transport level (HTTP/FTP/IRC/Mail, etc),
>> one for inline scripting (I'm still dreaming about Midgard integration
>> with Perl for doing non-web based things like scientific conference
>> management which has not only Web but many other sides). There will be
>> also wrappers for utilites like searching, spell checking, markup
>> converting which correctly converts Midgard-specific tags like &(var);
>> into form supported by target format+scripting (really far from now
>> idea), and many others which create content management
> What I've been thinking about lately is defining a CORBA based
> infrastructure in which services like the ones described above
> could be aggregated. The storage manager, security manager, and
> some others would be part of the core, and all other functionality
> (like midgard 1.2) would be applications against that core. The
> layout manager as it is in 1.2 could possibly be separated from
> the scripting environment to be offered as one of the core services.
> A protocol will need to be deviced for all basic services to allow
> generic searching etc.
I'm also thinking about it though precise technology is not defined
yet. CORBA is general solution but speed slowdown may be important.
The same we have for ODBC - Gene Sokolov already brightly outlined
conjectured problems.
> I don't know enough about the drawbacks of CORBA just now; I've
> picked up some books and have delved in. But this idea, if at
> all feasible, will allow applications to be developed against
> the midgard core, in pretty much any language of your choosing.
I'm looking forward for your investigation's results.
Best regards,
Alexander mailto:[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]
