On Thu, 2002-09-26 at 13:33, Ben Logan wrote:
> Hello,
>
> I successfully installed Webware on my Redhat 7.1 box a few days ago,
> but am having some trouble with a few concepts. Before I get into
> that, perhaps I should tell you what I would eventually like to
> accomplish using Webware.
>
> I created and maintain a website at http://cyclist.wblogan.net. You
> might want to take a look to get a feel for what I would like to do.
> My username is 'benl', and you can login with the pulldown menu on the
> left. The site is written in PHP with a MySQL backend. This was my
> first such project, and it shows! :) The code is nasty and
> unmaintainable, and the interface is crummy. I do have an improved
> version in the works on my own system, but I've pretty much ceased
> work on it. The new version is about 10,000 combined lines of
> PHP+HTML, and has a much more modular and layered design. However, I
> would *much* rather code this project in Python. It looks like
> WebWare could simplify the process for me. Is this a good candidate
> for an application server? If I'm understanding the concept behind an
> app server, the state of my application could remain intact between
> pages without me having to try to maintain it between pages. That's
> what I've been using sessions in PHP for, but it always seems to get
> complicated--especially when it comes to accepting/validating form
> data. Or maybe I'm just dense...
Yes, Webware would be appropriate for this sort of application. It's
still similar to PHP in terms of session data, but hopefully it would
still be simpler. I'd recommend you spend time putting all the hard
work (with the databases and statistics generation) into a plain Python
module (i.e., one that doesn't use Webware in any way). Then you can
use Webware servlets to provide an interface to this module. This will
help keep your code cleaner, and probably make the programming more
pleasant.
> I think I get most of the ideas from the examples provided with WebKit
> (and looking through the sources), but I'm mainly confused about
> transactions and the HTTP{Request,Response} classes. (OK, so there
> are a bunch more that I don't get, but those seem most relevant.) I'm
> just having some trouble getting started with WebKit--probably because
> I'm completely new to appservers in general.
Maybe you are thinking there is more to those objects than there really
is. They are actually quite simple objects -- Transaction is just a
holder for the HTTPRequest and HTTPResponse. The request and response
just hold input (form fields) and output (headers, cookies, and the body
of the page). If you want to get a feel for how WebKit as a whole
works, you might look at
http://webware.colorstudy.net/twiki/bin/view/Webware/TransactionAnatomy
-- however, you don't need to get to this depth to use WebKit (but it
might make you more comfortable with what's going on).
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
