I think that everything lies in the definition "web site vs web
application". Of course, the border is fuzzy and while it's easy to
differentiate "extreme" cases, it's difficult to give a precise definition.
A web site, to me, is something that mostly provides information, but
not services. If you manage to book an hotel by means of it, it's a web
application, not a website.
Given that, the original blog is... just obvious thing to me. I'm
running a number of websites, for my projects and my photos, and I've
been using a CMS since 2005.
If the post author is indeed using a larger definition of website than
me, then I'm curious. Clearly, with a CMS you can book an hotel - all
the major CMS allow dynamic parts, generally by integrating with some
server-side framework. But I don't see the reason for such a solution,
unless the webapplication part must be coupled with a conspicuous
website part.
PS BTW, one should keep in mind Brix, which is a CMS-oriented framework
for bulding webapplications with a strong CMS personality.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
