Ah, I guess I was confused about the fact I saw CGI mentioned a lot on the
So what you're saying is that you have your own HTTP server...
But, anyway - how hard do you think it would be to take PSPs and wrap/adapt
them to use from the Java environment (servlet container, essentially)?
Terell Shumway wrote:
> Interesting. I am going the other way: Java to Python.
Not sure what you mean by this - I am, also, in a way going from Java
(language) to Python (since I coded in Java before), except staying with
Java (the platform) in the end. I'm sure someone here has a healthy critique
for this idea :-).
>I am doing some proof-of-concept (mostly) development in Jython.
>Right now I'm approaching moving the interface of the application to Web
>and started to look at various ?SPs - e.g., JSPs, PSPs, WW PSPs.
>JSPs don't cut it (not Python, in short, but actually because the
>parameters it receives are somewhat faceless PyInstances).
>I don't like the "$[" syntax of PSPs, so WebWare PSPs seem like the best
>choice, EXCEPT they seem to be CGI-oriented.
No, Webware.PSP relies on Webware.WebKit which is a Python application
server featuring Python servlets.
In fact, I don't think you can use our PSP from CGI even if you wanted to.
BTW don't be deceived by the CGI *adapters*. These are small programs that
shuttle requests between the web server and the app server. OneShot.cgi is
convenient for development (for reasons explained in the Install Guide).
WebKit.cgi there mostly for completeness.
Lately, I have been using mod_webkit which is very fast and works without