[DAISY] Updated: Overview

A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1412.html

Document ID: 1412
Branch: main
Language: default
Name: Overview (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/12/08 9:41:26 PM
Updated by: Grzegorz Kossakowski

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 6682 bytes (previous version: 5554 bytes)
Content diff:
(161 equal lines skipped)
    </tbody>
    </table>
    
+++ <p>Being aware of mapping between OOP and ROA let's see how SSF implementing
+++ these ideas looks in action.</p>
+++ 
+++ <p align="center"><img src="daisy:1429"/></p>
+++ 
+++ <p>Now few remarks are needed:</p>
+++ 
+++ <ul>
+++ <li>Diagram above shows the situation when original request comes from browser
+++ (or other external program) and is handled by DispatcherServlet first. If
+++ request is being made by servlet using connection it would look similar to this
+++ one. It turns out that connection object is not a trivial object linking two
+++ servlets because it's connection's job to make all this magic of dispatching
+++ request to the super servlet if original one does not handle requested resource.
+++ </li>
+++ <li>Servlet B returns 404 status code as response and this simply means that
+++ Servlet B does not override handling of /foo/bar resource from servlet A. If
+++ servlet B had returned 200 status code, then DispatcherServlet would not make a
+++ second request to servlet A and would finish with response got from Servlet B.
+++ </li>
+++ <li>Mulitple levels of inheritance are possible (servlet A could connect to
+++ another servlet with connection named "super").</li>
+++ </ul>
+++ 
    </body>
    </html>