Skip to content

Z
Zope
Commit eab98097 authored by Amos Latteier's avatar Amos Latteier
Browse files
Options

New changes and readme for second alpha of ZServer.

parent 9c84c3a7
Hide whitespace changes
Inline Side-by-side
Showing with 560 additions and 386 deletions
ZServer/CHANGES.txt
View file @ eab98097
...@@ -6,13 +6,42 @@ ZServer Changes ...@@ -6,13 +6,42 @@ ZServer Changes
Releases Releases
Zserver 1.0a1 ZServer 1.0a2
New Features New Features
Inital release. Includes new threaded architecture--currently Preliminary support for PCGI has been added. It is still not
complete and bug free. The main problem is that all newlines
seem to get converted to carriage return newline pairs...
Simple controls to limit FTP connections have been added to
help prevent denial of service attacks.
FTP now supports login with a username and directory, i.e.
'joe@Projects/JoesProject' which authenticates the login in
the specified directory. You can still use a normal username
and defer authentication until you cd to a directory where you
are defined.
Bug Fixed
Data was being dropped from POST requests because of a bug in
the sized input collection of asynchat.
HTTP Response headers were not being correctly set.
URL prefixes for the the Zope HTTP handler could not be set to
''. Now the empty prefix is the default, to simplify URLs.
ZServer 1.0a1
New Features
Initial release. Includes new threaded architecture--currently
limited to a thread pool of 1. Includes preliminary FTP limited to a thread pool of 1. Includes preliminary FTP
support. Includes HTTP support. support. Includes HTTP support.
Bugs Fixed Bugs Fixed
None
ZServer/README.txt
View file @ eab98097
ZServer Release 1.0a1 ZServer Release 1.0a2
--------------------- ---------------------
Welcome to the first Zope ZServer alpha release. This release provides Welcome to the second Zope ZServer alpha release. This release
a first look at Zope/Medusa integration, and introduces FTP support in provides a first look at Zope/Medusa integration, and introduces FTP
Zope. support in Zope.
What is ZServer? What is ZServer?
ZServer is an integration of the Zope application server and the ZServer is an integration of the Zope application server and the
Medusa information server. See the ZServer architecture document for Medusa information server. See the ZServer architecture document for
more information.:: more information::
http://www.zope.org/Documentation/Reference/ZServer http://www.zope.org/Documentation/Reference/ZServer
ZServer gives you HTTP and FTP access. In later releases it will ZServer gives you HTTP, FTP, and PCGI access. In later releases it
probably offer more protocols such as PCGI, WebDAV, etc. will probably offer more protocols such as FastCGI, WebDAV, etc.
What is Medusa? What is Medusa?
Medusa is a Python server framework with uses a single threaded Medusa is a Python server framework with uses a single threaded
asynchronous sockets approach. For more information see:: asynchronous sockets approach. For more information see::
http://www.nightmare.com/medusa http://www.nightmare.com/medusa
There's also an interesting Medusa tutorial at:: There's also an interesting Medusa tutorial at::
http://www.nightmare.com:8080/nm/apps/medusa/docs/programming.html http://www.nightmare.com:8080/nm/apps/medusa/docs/programming.html
ZServer FTP support ZServer FTP support
FTP access to Zope allows you to FTP to the Zope object hierarchy in What you can do with FTP
order to perform managerial tasks. You can:
FTP access to Zope allows you to FTP to the Zope object hierarchy
* Navigate the object hierarchy with 'cd' in order to perform managerial tasks. You can:
* Replace the content of Documents, Images, and Files
* Create Documents, Images, Files, Folders * Navigate the object hierarchy with 'cd'
* Delete any sort of object
* Replace the content of Documents, Images, and Files
So basically you can do more than is possible with PUT. Also, unlike
PUT, FTP gives you access to Document content. So when you download * Create Documents, Images, Files, Folders
a Document you are getting its content, not what it looks like when
it rendered. * Delete any sort of object
FTP permissions So basically you can do more than is possible with PUT. Also,
unlike PUT, FTP gives you access to Document content. So when you
FTP support is provided for Folders, Documents, Images, and Files. download a Document you are getting its content, not what it looks
You can control access to FTP via the new 'FTP access' permission. like when it rendered.
This permission controls the ability to 'cd' to a Folder and to
download objects. Uploading and deleting and creating objects are Using FTP
controlled by existing permissions.
To FTP into Zope, ZServer must be configured to serve FTP. By
Properties and FTP: The next step default ZServer serves FTP on port 8021. So to connect to Zope you
would issue a command like so::
The next phase of FTP support will allow you to edit properties of
all Zope objects. Probably properties will be exposed via special ftp localhost 8021
files which will contain an XML representation of the object's
properties. You could then download the file, edit the XML and When logging in to FTP, you have some choices. You can connect
upload it to change the object's properties. anonymously by using a username of 'anonymous' and any password.
Or you can login as a Zope user. Since Zope users are defined at
We do not currently have a target date for FTP property support. different locations in the object hierarchy, authentication can be
It will probably need to wait until Zope has property sheets. problematic. There are two solutions:
Differences between ZopeHTTPServer and ZServer * login and then cd to the directory where you are defined.
Both ZopeHTTPServer and ZServer are Python HTTP servers. * login with a special name that indicates where you are
ZopeHTTPServer is built on the standard Python SimpleHTTPServer defined.
framework. ZServer is built on Medusa.
The format of the special name is <username>@<path>. For example::
ZopeHTTPServer is very limited. It can only publish one module at a
time. It can only publish via HTTP. It has no support for thread joe@Marketing/Projects
pools. And more importantly, it is no longer being actively
developed, since its author has moved on the ZServer. FTP permissions
ZServer on the other hand is more complex and supports publishing FTP support is provided for Folders, Documents, Images, and Files.
multiple modules, thread pools, and it uses a new threaded You can control access to FTP via the new 'FTP access' permission.
architecture for accessing ZPublisher. Right now the thread pool is This permission controls the ability to 'cd' to a Folder and to
limited to one thread, since the object database cannot yet support download objects. Uploading and deleting and creating objects are
concurrent access. This should change within the next few months. controlled by existing permissions.
How does FTP work? FTP limits
The ZServer's FTP channel object translates FTP requests into You can set limits for the number of simultaneous FTP connections.
ZPublisher requests. The FTP channel then analyses the response and You can separately configure the number of anonymous and
formulates an appropriate FTP response. The FTP channel stores some authenticated connections. Right now this setting is set in
state such as the current working directory and the username and 'ZServerFTP.py'. In the future, it may be more easy to configure.
password.
Properties and FTP: The next step
On the Zope side of things, the 'FTPSupport.py' module provides a
few mix-in classes for Document, Folder, and File (which Image The next phase of FTP support will allow you to edit properties of
inherits from). These mix in classes provide directory listing and all Zope objects. Probably properties will be exposed via special
stat-like methods. All the other FTP functions are handled by files which will contain an XML representation of the object's
existing methods like 'manage_delObjects', and 'PUT', etc. properties. You could then download the file, edit the XML and
upload it to change the object's properties.
Who should use ZServer?
We do not currently have a target date for FTP property support.
This release is *alpha* quality. It should be used by Zope hackers. It will probably need to wait until Zope has property sheets.
If you are not inquisitive and self-reliant, this release will
frustrate you. How does FTP work?
Installation The ZServer's FTP channel object translates FTP requests into
ZPublisher requests. The FTP channel then analyses the response
To install ZServer you need to do two things: edit the start script and formulates an appropriate FTP response. The FTP channel
and update some Zope files to introduce FTP support. stores some state such as the current working directory and the
username and password.
To edit the start up script, open 'start.py' in your favorite editor
and change the configuration variables. If you understand Medusa, On the Zope side of things, the 'lib/python/OFS/FTPInterface.py'
you can also change the rest of the script. module defines the Zope FTP interface, for listing sub-items,
stating, and getting content. The interface is implemented in
To enable FTP support in Zope you need to update some files in 'SimpleItem', and in other Zope classes. Programmers will not
'lib/python/OFS'. You should probably first back up your 'OFS' need to implement the entire interface if they inherit from
directory, or at least make copies of the files that will be 'SimpleItem'. All the other FTP functions are handled by
replaced ('Document.py', 'Image.py', 'Folder.py'). Then copy the existing methods like 'manage_delObjects', and 'PUT', etc.
contents of ZServer's 'OFS' directory to your Zope 'lib/python/OFS'
directory. ZServer PCGI support
Finally make sure the shebang line is right on the start script. You ZServer will service PCGI requests with both inet and unix domain
can use your own copy of Python, or the copy that came with Zope (if sockets. This means you can use ZServer instead of
you are using a binary distribution). 'pcgi_publisher.py' as your long running PCGI server process. In the
future, PCGI may be able to activate ZServer.
Now your ready to go.
Using PCGI instead of HTTP allows you to forward requests from
Usage another web server to ZServer. The CGI environment and HTTP headers
are controlled by the web server, so you don't need to worry about
To start ZServer run the start script:: managing the ZServer environment. However, this configuration will
impose a larger overhead than simply using the web server as an HTTP
./start.py proxy for ZServer.
To stop the server type 'control-c'. PCGI support in ZServer is still incomplete.
You should see some logging information come up on the screen. To use PCGI, configure your PCGI info files to communicate with
ZServer by setting the PCGI_PORT, PCGI_SOCKET_FILE, and PCGI_NAME.
Once you start ZServer is will publish Zope (or any Python module) The other PCGI settings are currently ignored by ZServer.
on HTTP and/or FTP. To access Zope via HTTP point your browser at
the server like so:: Differences between ZopeHTTPServer and ZServer
http://www.example.com:9673/Main Both ZopeHTTPServer and ZServer are Python HTTP servers.
ZopeHTTPServer is built on the standard Python SimpleHTTPServer
This assumes that you have chosen to put HTTP on port 9673 and that framework. ZServer is built on Medusa.
you are publishing a module named 'Main'. Note: to publish Zope
normally you publish the 'lib/python/Main.py' module. ZopeHTTPServer is very limited. It can only publish one module at a
time. It can only publish via HTTP. It has no support for thread
To access Zope via FTP you need to FTP to it at the port you set FTP pools. And more importantly, it is no longer being actively
to run on. For example:: developed, since its author has moved on the ZServer.
ftp www.example.com 8021 ZServer on the other hand is more complex and supports publishing
multiple modules, thread pools, and it uses a new threaded
This starts and FTP session to your machine on port 8021, ZServer's architecture for accessing ZPublisher. Right now the thread pool is
default FTP port. When you are prompted to log in you should supply limited to one thread, since the object database cannot yet support
a Zope username and password. (Probably you should use an account concurrent access. This should change within the next few months.
with the 'Manager' role, unless you have configured Zope to allow
FTP access to the 'Anonymous' role.) You can also enter 'anonymous' Who should use ZServer?
and any password for anonymous FTP access. Once you have logged in
you can start issuing normal FTP commands. Right now ZServer only This release is *alpha* quality. It should be used by Zope hackers.
supports basic FTP commands. Note: When you log in your working If you are not inquisitive and self-reliant, this release may
directory is set to '/'. If you do not have FTP permissions in this frustrate you.
directory, you will need to 'cd' to a directory where you have
permissions before you can do anything. Installation
Support To run ZServer you need to edit the start script to set your
configuration. In the future will will probably provide a customized
Questions and comments should go to 'support@digicool.com'. start script as part of the Zope installtion process.
You can report bugs and check on the status of bugs using the Zope To edit the start up script, open 'ZServer/start.py' in your
bug collector.:: favorite editor and change the configuration variables. If you
understand Medusa, you can also change the rest of the script.
http://www.zope.org/Collector/
Finally make sure the shebang line is right on the 'start.py'
License script. You can use your own copy of Python, or the copy that came
with Zope (if you are using a binary distribution). If you are using
ZServer is covered by the ZPL despite the fact that it comes with win32, you might want to create a bat file to run the 'start.py'
much of the Medusa source code. The portions of Medusa that come program with Zope's Python.
with ZServer are licensed under the ZPL.
Now you're ready to go.
Outstanding issues
Usage
PCGI support is not done yet. The FTP interface for Zope objects may
be changed, i.e. 'manage_FTPlist' and 'manage_FTPstat' maybe changed To start ZServer run the start script::
and/or renamed. When FTP support for properties is added, this may
change a lot. WebDAV support will also probably cause a little ./start.py
reorganization.
To stop the server type 'control-c'.
Currently ZServer's Medusa files are a bit modified from the
originals. It would be good idea to try and keep deviations to a You should see some Medusa information come up on the screen.
minimum. For this reason we have been feeding bug reports and change
requests back to Sam Rushing for inclusion in the official Medusa A log file will be written, named 'ZServer.log' by default.
souces. It is possible, however, that Medusa and ZServer will
diverge in some small respects despite our best efforts to keep them Once you start ZServer is will publish Zope (or any Python module)
unified. One area in particular where ZServer currently departs from on HTTP and/or FTP. To access Zope via HTTP point your browser at
Medusa is in the use of future producers. Change is likely in the server like so::
ZServer's use of future producers.
http://www.example.com:9673/
This assumes that you have chosen to put HTTP on port 9673 and that
you are publishing a module named whose URL prefix is set to ''.
Note: to publish Zope normally you publish the 'lib/python/Main.py'
module.
To access Zope via FTP you need to FTP to it at the port you set FTP
to run on. For example::
ftp www.example.com 8021
This starts and FTP session to your machine on port 8021, ZServer's
default FTP port. When you are prompted to log in you should supply
a Zope username and password. (Probably you should use an account
with the 'Manager' role, unless you have configured Zope to allow
FTP access to the 'Anonymous' role.) You can also enter 'anonymous'
and any password for anonymous FTP access. Once you have logged in
you can start issuing normal FTP commands. Right now ZServer only
supports basic FTP commands. Note: When you log in your working
directory is set to '/'. If you do not have FTP permissions in this
directory, you will need to 'cd' to a directory where you have
permissions before you can do anything. See above for more
information about logging into FTP.
Support
Questions and comments should go to 'support@digicool.com'.
You can report bugs and check on the status of bugs using the Zope
bug collector::
http://www.zope.org/Collector/
License
ZServer is covered by the ZPL despite the fact that it comes with
much of the Medusa source code. The portions of Medusa that come
with ZServer are licensed under the ZPL.
Outstanding issues
PCGI support is buggy. The FTP interface for Zope objects may be
changed, i.e. 'manage_FTPlist' and 'manage_FTPstat' maybe changed
and/or renamed. When FTP support for properties is added, this may
change a lot. WebDAV support will also probably cause a little
reorganization.
Currently ZServer's Medusa files are a bit modified from the
originals. It would be good idea to try and keep deviations to a
minimum. For this reason we have been feeding bug reports and change
requests back to Sam Rushing for inclusion in the official Medusa
sources. It is possible, however, that Medusa and ZServer will
diverge in some small respects despite our best efforts to keep them
unified. One area in particular where ZServer currently departs from
Medusa is in the use of future producers. Change is likely in
ZServer's use of future producers.
lib/python/ZServer/CHANGES.txt
View file @ eab98097
...@@ -6,13 +6,42 @@ ZServer Changes ...@@ -6,13 +6,42 @@ ZServer Changes
Releases Releases
Zserver 1.0a1 ZServer 1.0a2
New Features New Features
Inital release. Includes new threaded architecture--currently Preliminary support for PCGI has been added. It is still not
complete and bug free. The main problem is that all newlines
seem to get converted to carriage return newline pairs...
Simple controls to limit FTP connections have been added to
help prevent denial of service attacks.
FTP now supports login with a username and directory, i.e.
'joe@Projects/JoesProject' which authenticates the login in
the specified directory. You can still use a normal username
and defer authentication until you cd to a directory where you
are defined.
Bug Fixed
Data was being dropped from POST requests because of a bug in
the sized input collection of asynchat.
HTTP Response headers were not being correctly set.
URL prefixes for the the Zope HTTP handler could not be set to
''. Now the empty prefix is the default, to simplify URLs.
ZServer 1.0a1
New Features
Initial release. Includes new threaded architecture--currently
limited to a thread pool of 1. Includes preliminary FTP limited to a thread pool of 1. Includes preliminary FTP
support. Includes HTTP support. support. Includes HTTP support.
Bugs Fixed Bugs Fixed
None
lib/python/ZServer/README.txt
View file @ eab98097
ZServer Release 1.0a1 ZServer Release 1.0a2
--------------------- ---------------------
Welcome to the first Zope ZServer alpha release. This release provides Welcome to the second Zope ZServer alpha release. This release
a first look at Zope/Medusa integration, and introduces FTP support in provides a first look at Zope/Medusa integration, and introduces FTP
Zope. support in Zope.
What is ZServer? What is ZServer?
ZServer is an integration of the Zope application server and the ZServer is an integration of the Zope application server and the
Medusa information server. See the ZServer architecture document for Medusa information server. See the ZServer architecture document for
more information.:: more information::
http://www.zope.org/Documentation/Reference/ZServer http://www.zope.org/Documentation/Reference/ZServer
ZServer gives you HTTP and FTP access. In later releases it will ZServer gives you HTTP, FTP, and PCGI access. In later releases it
probably offer more protocols such as PCGI, WebDAV, etc. will probably offer more protocols such as FastCGI, WebDAV, etc.
What is Medusa? What is Medusa?
Medusa is a Python server framework with uses a single threaded Medusa is a Python server framework with uses a single threaded
asynchronous sockets approach. For more information see:: asynchronous sockets approach. For more information see::
http://www.nightmare.com/medusa http://www.nightmare.com/medusa
There's also an interesting Medusa tutorial at:: There's also an interesting Medusa tutorial at::
http://www.nightmare.com:8080/nm/apps/medusa/docs/programming.html http://www.nightmare.com:8080/nm/apps/medusa/docs/programming.html
ZServer FTP support ZServer FTP support
FTP access to Zope allows you to FTP to the Zope object hierarchy in What you can do with FTP
order to perform managerial tasks. You can:
FTP access to Zope allows you to FTP to the Zope object hierarchy
* Navigate the object hierarchy with 'cd' in order to perform managerial tasks. You can:
* Replace the content of Documents, Images, and Files
* Create Documents, Images, Files, Folders * Navigate the object hierarchy with 'cd'
* Delete any sort of object
* Replace the content of Documents, Images, and Files
So basically you can do more than is possible with PUT. Also, unlike
PUT, FTP gives you access to Document content. So when you download * Create Documents, Images, Files, Folders
a Document you are getting its content, not what it looks like when
it rendered. * Delete any sort of object
FTP permissions So basically you can do more than is possible with PUT. Also,
unlike PUT, FTP gives you access to Document content. So when you
FTP support is provided for Folders, Documents, Images, and Files. download a Document you are getting its content, not what it looks
You can control access to FTP via the new 'FTP access' permission. like when it rendered.
This permission controls the ability to 'cd' to a Folder and to
download objects. Uploading and deleting and creating objects are Using FTP
controlled by existing permissions.
To FTP into Zope, ZServer must be configured to serve FTP. By
Properties and FTP: The next step default ZServer serves FTP on port 8021. So to connect to Zope you
would issue a command like so::
The next phase of FTP support will allow you to edit properties of
all Zope objects. Probably properties will be exposed via special ftp localhost 8021
files which will contain an XML representation of the object's
properties. You could then download the file, edit the XML and When logging in to FTP, you have some choices. You can connect
upload it to change the object's properties. anonymously by using a username of 'anonymous' and any password.
Or you can login as a Zope user. Since Zope users are defined at
We do not currently have a target date for FTP property support. different locations in the object hierarchy, authentication can be
It will probably need to wait until Zope has property sheets. problematic. There are two solutions:
Differences between ZopeHTTPServer and ZServer * login and then cd to the directory where you are defined.
Both ZopeHTTPServer and ZServer are Python HTTP servers. * login with a special name that indicates where you are
ZopeHTTPServer is built on the standard Python SimpleHTTPServer defined.
framework. ZServer is built on Medusa.
The format of the special name is <username>@<path>. For example::
ZopeHTTPServer is very limited. It can only publish one module at a
time. It can only publish via HTTP. It has no support for thread joe@Marketing/Projects
pools. And more importantly, it is no longer being actively
developed, since its author has moved on the ZServer. FTP permissions
ZServer on the other hand is more complex and supports publishing FTP support is provided for Folders, Documents, Images, and Files.
multiple modules, thread pools, and it uses a new threaded You can control access to FTP via the new 'FTP access' permission.
architecture for accessing ZPublisher. Right now the thread pool is This permission controls the ability to 'cd' to a Folder and to
limited to one thread, since the object database cannot yet support download objects. Uploading and deleting and creating objects are
concurrent access. This should change within the next few months. controlled by existing permissions.
How does FTP work? FTP limits
The ZServer's FTP channel object translates FTP requests into You can set limits for the number of simultaneous FTP connections.
ZPublisher requests. The FTP channel then analyses the response and You can separately configure the number of anonymous and
formulates an appropriate FTP response. The FTP channel stores some authenticated connections. Right now this setting is set in
state such as the current working directory and the username and 'ZServerFTP.py'. In the future, it may be more easy to configure.
password.
Properties and FTP: The next step
On the Zope side of things, the 'FTPSupport.py' module provides a
few mix-in classes for Document, Folder, and File (which Image The next phase of FTP support will allow you to edit properties of
inherits from). These mix in classes provide directory listing and all Zope objects. Probably properties will be exposed via special
stat-like methods. All the other FTP functions are handled by files which will contain an XML representation of the object's
existing methods like 'manage_delObjects', and 'PUT', etc. properties. You could then download the file, edit the XML and
upload it to change the object's properties.
Who should use ZServer?
We do not currently have a target date for FTP property support.
This release is *alpha* quality. It should be used by Zope hackers. It will probably need to wait until Zope has property sheets.
If you are not inquisitive and self-reliant, this release will
frustrate you. How does FTP work?
Installation The ZServer's FTP channel object translates FTP requests into
ZPublisher requests. The FTP channel then analyses the response
To install ZServer you need to do two things: edit the start script and formulates an appropriate FTP response. The FTP channel
and update some Zope files to introduce FTP support. stores some state such as the current working directory and the
username and password.
To edit the start up script, open 'start.py' in your favorite editor
and change the configuration variables. If you understand Medusa, On the Zope side of things, the 'lib/python/OFS/FTPInterface.py'
you can also change the rest of the script. module defines the Zope FTP interface, for listing sub-items,
stating, and getting content. The interface is implemented in
To enable FTP support in Zope you need to update some files in 'SimpleItem', and in other Zope classes. Programmers will not
'lib/python/OFS'. You should probably first back up your 'OFS' need to implement the entire interface if they inherit from
directory, or at least make copies of the files that will be 'SimpleItem'. All the other FTP functions are handled by
replaced ('Document.py', 'Image.py', 'Folder.py'). Then copy the existing methods like 'manage_delObjects', and 'PUT', etc.
contents of ZServer's 'OFS' directory to your Zope 'lib/python/OFS'
directory. ZServer PCGI support
Finally make sure the shebang line is right on the start script. You ZServer will service PCGI requests with both inet and unix domain
can use your own copy of Python, or the copy that came with Zope (if sockets. This means you can use ZServer instead of
you are using a binary distribution). 'pcgi_publisher.py' as your long running PCGI server process. In the
future, PCGI may be able to activate ZServer.
Now your ready to go.
Using PCGI instead of HTTP allows you to forward requests from
Usage another web server to ZServer. The CGI environment and HTTP headers
are controlled by the web server, so you don't need to worry about
To start ZServer run the start script:: managing the ZServer environment. However, this configuration will
impose a larger overhead than simply using the web server as an HTTP
./start.py proxy for ZServer.
To stop the server type 'control-c'. PCGI support in ZServer is still incomplete.
You should see some logging information come up on the screen. To use PCGI, configure your PCGI info files to communicate with
ZServer by setting the PCGI_PORT, PCGI_SOCKET_FILE, and PCGI_NAME.
Once you start ZServer is will publish Zope (or any Python module) The other PCGI settings are currently ignored by ZServer.
on HTTP and/or FTP. To access Zope via HTTP point your browser at
the server like so:: Differences between ZopeHTTPServer and ZServer
http://www.example.com:9673/Main Both ZopeHTTPServer and ZServer are Python HTTP servers.
ZopeHTTPServer is built on the standard Python SimpleHTTPServer
This assumes that you have chosen to put HTTP on port 9673 and that framework. ZServer is built on Medusa.
you are publishing a module named 'Main'. Note: to publish Zope
normally you publish the 'lib/python/Main.py' module. ZopeHTTPServer is very limited. It can only publish one module at a
time. It can only publish via HTTP. It has no support for thread
To access Zope via FTP you need to FTP to it at the port you set FTP pools. And more importantly, it is no longer being actively
to run on. For example:: developed, since its author has moved on the ZServer.
ftp www.example.com 8021 ZServer on the other hand is more complex and supports publishing
multiple modules, thread pools, and it uses a new threaded
This starts and FTP session to your machine on port 8021, ZServer's architecture for accessing ZPublisher. Right now the thread pool is
default FTP port. When you are prompted to log in you should supply limited to one thread, since the object database cannot yet support
a Zope username and password. (Probably you should use an account concurrent access. This should change within the next few months.
with the 'Manager' role, unless you have configured Zope to allow
FTP access to the 'Anonymous' role.) You can also enter 'anonymous' Who should use ZServer?
and any password for anonymous FTP access. Once you have logged in
you can start issuing normal FTP commands. Right now ZServer only This release is *alpha* quality. It should be used by Zope hackers.
supports basic FTP commands. Note: When you log in your working If you are not inquisitive and self-reliant, this release may
directory is set to '/'. If you do not have FTP permissions in this frustrate you.
directory, you will need to 'cd' to a directory where you have
permissions before you can do anything. Installation
Support To run ZServer you need to edit the start script to set your
configuration. In the future will will probably provide a customized
Questions and comments should go to 'support@digicool.com'. start script as part of the Zope installtion process.
You can report bugs and check on the status of bugs using the Zope To edit the start up script, open 'ZServer/start.py' in your
bug collector.:: favorite editor and change the configuration variables. If you
understand Medusa, you can also change the rest of the script.
http://www.zope.org/Collector/
Finally make sure the shebang line is right on the 'start.py'
License script. You can use your own copy of Python, or the copy that came
with Zope (if you are using a binary distribution). If you are using
ZServer is covered by the ZPL despite the fact that it comes with win32, you might want to create a bat file to run the 'start.py'
much of the Medusa source code. The portions of Medusa that come program with Zope's Python.
with ZServer are licensed under the ZPL.
Now you're ready to go.
Outstanding issues
Usage
PCGI support is not done yet. The FTP interface for Zope objects may
be changed, i.e. 'manage_FTPlist' and 'manage_FTPstat' maybe changed To start ZServer run the start script::
and/or renamed. When FTP support for properties is added, this may
change a lot. WebDAV support will also probably cause a little ./start.py
reorganization.
To stop the server type 'control-c'.
Currently ZServer's Medusa files are a bit modified from the
originals. It would be good idea to try and keep deviations to a You should see some Medusa information come up on the screen.
minimum. For this reason we have been feeding bug reports and change
requests back to Sam Rushing for inclusion in the official Medusa A log file will be written, named 'ZServer.log' by default.
souces. It is possible, however, that Medusa and ZServer will
diverge in some small respects despite our best efforts to keep them Once you start ZServer is will publish Zope (or any Python module)
unified. One area in particular where ZServer currently departs from on HTTP and/or FTP. To access Zope via HTTP point your browser at
Medusa is in the use of future producers. Change is likely in the server like so::
ZServer's use of future producers.
http://www.example.com:9673/
This assumes that you have chosen to put HTTP on port 9673 and that
you are publishing a module named whose URL prefix is set to ''.
Note: to publish Zope normally you publish the 'lib/python/Main.py'
module.
To access Zope via FTP you need to FTP to it at the port you set FTP
to run on. For example::
ftp www.example.com 8021
This starts and FTP session to your machine on port 8021, ZServer's
default FTP port. When you are prompted to log in you should supply
a Zope username and password. (Probably you should use an account
with the 'Manager' role, unless you have configured Zope to allow
FTP access to the 'Anonymous' role.) You can also enter 'anonymous'
and any password for anonymous FTP access. Once you have logged in
you can start issuing normal FTP commands. Right now ZServer only
supports basic FTP commands. Note: When you log in your working
directory is set to '/'. If you do not have FTP permissions in this
directory, you will need to 'cd' to a directory where you have
permissions before you can do anything. See above for more
information about logging into FTP.
Support
Questions and comments should go to 'support@digicool.com'.
You can report bugs and check on the status of bugs using the Zope
bug collector::
http://www.zope.org/Collector/
License
ZServer is covered by the ZPL despite the fact that it comes with
much of the Medusa source code. The portions of Medusa that come
with ZServer are licensed under the ZPL.
Outstanding issues
PCGI support is buggy. The FTP interface for Zope objects may be
changed, i.e. 'manage_FTPlist' and 'manage_FTPstat' maybe changed
and/or renamed. When FTP support for properties is added, this may
change a lot. WebDAV support will also probably cause a little
reorganization.
Currently ZServer's Medusa files are a bit modified from the
originals. It would be good idea to try and keep deviations to a
minimum. For this reason we have been feeding bug reports and change
requests back to Sam Rushing for inclusion in the official Medusa
sources. It is possible, however, that Medusa and ZServer will
diverge in some small respects despite our best efforts to keep them
unified. One area in particular where ZServer currently departs from
Medusa is in the use of future producers. Change is likely in
ZServer's use of future producers.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7