Ian, Looks good, here are some comments.
There are a couple of significantly different ways to setup and run Webware.
1) Use of global access to Webware with mod_webkit and httpd.conf
referring a path such as /WK to Webware.
2) Use of global access to Webware/PSP with mod_webkit and
httpd.conf redirecting .psp pages to Webware. However this
does not currently work with PSP documents under ~user
locations.
3) Localized access where the .htaccess file redirects references
through the webkit-handler. Requires mod_webkit be installed
globally in httpd.conf but allows .htaccess references to
unique Webware AppServer by specifying the port to use. Note
that this may currently have problems with ~user expansion too.
4) Localized access to PSP through psp-handler references
in .htaccess file. Requires mod_webkit be installed globally
but allows .htaccess to reference a unique AppServer instance
by specifying the port to use. Note that this is broken
currently when using ~user expansion, but a fix is in the works.
5) Access through WebKit.cgi. I am not clear of the issues here
but believe there may be some problems with ~user expansion
here as well.
6) Access through OneShot.cgi
The options 1 and 2 above seem to be common. However I believe that the
other options also have value, especially if an ISP wants to offer Webware,
and allow users to reference their own instance of Webware.
The problems I pointed out with the ~user expansion tell me that currently,
not many people are trying to use it in that type of an environment. But I
think the potential for large scale use there is high.
I think it would be useful for the descriptions of setting up the
environment to outline the various ways in which Webware can be invoked, and
provide a brief description.
Also, given the discussions around referencing python vs python2, and the
requirement for python2, I think this should be clearly addressed.
Unfortunately some distro's (RedHat) have "python" invoking python 1.5.2
still. That will cause problems for someone unless we automagically fix it
to reference python2.
-Stuart-
> -----Original Message-----
> From: Ian Bicking [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 24, 2002 8:52 PM
> To: Webware Discuss
> Subject: [Webware-discuss] New documentation: Application Development
>
>
> I added some documentation today that gives some advice on
> application
> development with Webware, mostly MakeAppWorkDir with a little
> on CVS.
> I'd be interested on feedback -- I'd like this to become the
> basis for
> some conventions on distributing and handling Webware
> applications. If
> there's other topics that seem appropriate, or whatever.
> Documentation
> and enhancements can also go hand-in-hand -- some things might not be
> described because there's no one good way to do them in Webware; we
> might be able to fix those and document them at the same time.
>
> The document is in CVS at
> WebKit/Docs/ApplicationDevelopment.html (the
> .txt is the canonical source), or online at:
> http://tinyurl.com/3tfl
>
> Ian
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Webware-discuss mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/webware-discuss
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
