Porcupine wiki | Articles / The Porcupine Request Processing Pipeline

November 01, 2005, at 10:59 PM by Tassos Koutsovassilis -

Changed lines 36-37 from:

Diagram 1

to:

Diagram 1 - The Porcupine request processing pipeline

November 01, 2005, at 10:55 PM by Tassos Koutsovassilis -

Changed lines 36-37 from:

to:

Diagram 1

November 01, 2005, at 10:52 PM by Tassos Koutsovassilis -

Added lines 36-37:

November 01, 2005, at 10:42 PM by Tassos Koutsovassilis -

Changed lines 8-15 from:

to:

Changed lines 32-33 from:

 http://server/porcupine.py/{ab9e44738ce39448c8b245d6706dea9a}/Administrative Tools/Users and Groups/Administrators

to:

 http://server/porcupine.py/{ab9e44738ce39448c8b245d6706dea9a}/
 Administrative Tools/Users and Groups/Administrators

Changed lines 36-39 from:

to:

Changed lines 54-57 from:

to:

Changed lines 66-67 from:

to:

Changed lines 83-85 from:

to:

November 01, 2005, at 10:38 PM by Tassos Koutsovassilis -

Changed lines 3-4 from:

Knowing the steps taken by Porcupine before a servlet is executed, will help you understand one of the most important internal mechanisms. This article describes the server's execution plan from the moment a client request is picked up from the queue until the response is sent back to the web connector and then back to the client.

to:

Knowing the steps taken by Porcupine before a servlet is executed, will help you understand one of the most important internal mechanisms. This article describes the server's execution plan from the moment a client request is picked up from the queue until the response is sent back to the web connector and then back to the client.

Changed lines 12-13 from:

Porcupine objects can be addressed by using the object's ID or the full path. The latter is slower, since the server retrieves all the objects contained in the path by their display name, but more readable. Some examples of HTTP requests that address Porcupine objects are:

to:

Porcupine objects can be addressed by using the object's ID or the full path. The latter is slower, since the server retrieves all the objects contained in the path by their display name, but more readable. Some examples of HTTP requests that address Porcupine objects are:

November 01, 2005, at 10:35 PM by Tassos Koutsovassilis -

Changed lines 1-2 from:

title The Porcupine Request Processing Pipiline

to:

(:title The Porcupine Request Processing Pipeline:)

Changed line 29 from:

action: the servlet to be executed

to:

action: the servlet to be executed of the path to the PSP page

Changed lines 36-37 from:

http://server/porcupine.py/__xul/xul_core.js

to:

 http://server/porcupine.py/__xul/xul_core.js

Changed lines 40-42 from:

to:

 <context path="xul_core.js" method="GET" client="Netscape/7|Mozilla/5.0" lang=".*"
 action="core_moz.js" filters="porcupine.filters.postprocessing.Gzip" />

Changed lines 45-50 from:

to:

path: the path requested inside this published directory
method: the HTTP method of the request
client: the string that identifies the client that has submitted the request (regular expressions accepted)
action: the file to load or execute if it is a servlet
filters: semicolon separated list of post processing filters to apply, if any

November 01, 2005, at 10:33 PM by Tassos Koutsovassilis -

Changed lines 1-3 from:

title The Porcupine Request Processing Pipiline

Knowing the steps taken by Porcupine before a servlet is executed, will help you understand one of the most important internal mechanisms. This article describes the server's execution plan from the moment a client request is picked up from the queue until the response is sent back to the web connector and then back to the client.

to:

November 01, 2005, at 10:23 PM by Tassos Koutsovassilis -

Added lines 1-3:

(: title The Porcupine Request Processing Pipiline :)

Knowing the steps taken by Porcupine before a servlet is executed, will help you understand one of the most important internal mechanisms. This article describes the server's execution plan from the moment a client request is picked up from the queue until the response is sent back to the web connector and then back to the client.

The Porcupine Request Processing Pipeline

Articles.RequestProcessingPipeline History