Hey, sorry for all the silly questions...

Say I've got two very different sites on my server, held in
two contexts. I write a SitePage for each. Where do you put
these sitepages, how do you subclass them if you have
various directory structures under each context? I've
thought about this a bit, and have a few conflicting
thoughts. Wondering what you all do.

1. Have a server-wide Lib directory, as suggested in the
DirectoryStructure. Then I would import Lib.SiteA.SitePage,
assuming that root directory is in my sys.path. I guess I'd
prefer not to do this in order to keep all files associated
with a site together.

2. Assuming the contexts are all in a directory on my
sys.path, I could have separate Lib directories in each
context. Importing would be SiteA.Lib.SitePage. My concerns
here are that it makes all those imports dependent on the
directory structure and name of the context.

3. So what I'd prefer is to be able to set sys.path to
include the current context's directory. Then each
context/site could have its own Lib directory, importing as
Lib.SitePage. But there seem to be a lot of issues with
locking and cleaning up sys.path before and after import...

Unless I'm missing something simple, like AppServer already
creates little sandboxes for each context or something...

Thanks,

Luke

=====
------------------
Reference Counting Garbage Collection:
Look out philosophy majors, things really DO
cease to exist when no one is looking at them!
------------------

__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com

_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to