[Typo3-dev] Event System in the core / Ease the integration of 3rd party apps
Leendert Brouwer [Netcreators]
leendert at netcreators.nl
Fri Sep 3 11:45:33 CEST 2004
"Robert Lemke" <rl at robertlemke.de> wrote in message
news:mailman.1.1094203714.17382.typo3-dev at lists.netfielders.de...
> Hi Leendert,
>
> Leendert Brouwer [Netcreators] wrote:
>
> > I don't really see how webdav is related to it. Webdav has more to do
with
> > remote file access and versioning.
>
> Wouldn't that be useful for TYPO3 as well?
Well webdav is filesystem based, so that wouldn't make much sense for TYPO3.
Sure, versioning would be useful for TYPO3. I believe someone is working on
that? :)
>
> > LDAP does have to do with uniform user
> > management, or rather 'keeping it all in one place'. If every
application
> > out there used LDAP directories or had LDAP hooks for user management,
> > this kind of stuff would be easier.
>
> I'm not sure about the current status of the LDAP extension, doesn't that
> work?
It does, but it's not like TYPO3's user management relies on LDAP directly.
And third party applications usually don't either. I'm saying that if TYPO3
and third party applications all used LDAP for user management, then uniform
access would be guaranteed. That's one way, anyway.
>
> > If you ask me, content management systems that directly spit out
(x)html
> > have no future. Not in a device independent, personalized, unified
> > environment. So eventually, everything needs to speak with the CMS. And
> > that implies the need for changes just mentioned.
>
> So, what is the next step?
>
If you ask me, the next step is what Martin T. Kutschker mentioned and I
confirmed in a different post in this thread - having applications that only
have an API. No implementation of a View layer whatsoever. Any 'client'
could then talk to the application over e.g. XML. You'd only need to know
the protocol. Even makes upgrading/changing easier (as long as the protocol
is consistent, everything would be fine). XHTML only holds value when you
want marked up documents with hyperlinks etc. You really don't want to parse
XHTML with other applications. Browsers do it, but that's what they are made
for and that's all they do. You want to parse XML. Sure, currently the main
device approaching a CMS is a PC with a browser. But we're not that far away
from 'the internet is everything, and everything is the internet'. 3com
already did such projects, so did Sun (remember the toasters?), and I want
to do it too. IMHO, especially big content management systems such as TYPO3
should be prepared for the next step.
More information about the TYPO3-dev
mailing list