Zope excels at providing web services via XML-RPC. Basically: - You need to do exactly nothing to make a Zope application accessible via XML-RPC. - When Zope isn't responsible for rendering HTML, it can be quite fast. - Zope is capable of interfacing transactionally with many data stores. - C On Wed, 2005-08-17 at 12:59 +0100, Pascal Peregrina wrote:

Hi,

I know that this is an unusual request, but if some of you have some time to help me on this it would be great !

Basically, I can summarize the question I will have to answer this way : "why should we use Zope 2 instead of JSP/struts" ?

All the business logic of the company is implemented in services that talk to backend and can be queried through xmlrpc (so this is fine for Zope integration).

So the context is to use Zope or JSP/struts to manage the presentation layer.

I am currently planning to talk about built-in ZMI and transaction management, TAL, ...

Thanks a lot for your help.

Pascal

********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.

This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com **********************************************************************

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )