|
|
| Author |
Message |
|
| Guest |
 Posted: Fri Feb 23, 2007 6:44 pm |
 |
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 8:22 pm |
|
|
|
Guest
|
julian@precisium.com wrote:
> Hello All,
>
> I've checked in the 'virtual directory' code I mentioned earlier on
> this list.
>
> Here is an example of additions to a <server/> section of a yaws conf
> file:
>
> arg_rewrite_mod = yaws_vdir
> <opaque>
> vdir = "/virtual1/ /usr/local/somewhere/notrelated/to/main/docroot"
> vdir = "/myapp/ /some/other/path can include/spaces"
> vdir = "/icons/ /usr/local/www/yaws/icons"
> vdir = "/xyz/cgi-bin/ /usr/local/www/cgi-stuff"
> </opaque>
>
Good work, one single objection.
Don't use the #arg.opaque field, it's ment to be used for end user data.
This
is proper yaws data and thus deserves it's own field in the #arg record.
One more .. nag, The vdir stuff is really useful but I think it's non
trivial
to configure and ... worse to trouble shoot. So please make an effort at
documenting vdirs.
Cheers
/klacke
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Feb 25, 2007 7:29 am |
|
|
|
Guest
|
>
> Good work, one single objection.
>
> Don't use the #arg.opaque field, it's ment to be used for end user data.
> This
> is proper yaws data and thus deserves it's own field in the #arg record.
Sorry about that. I mentioned in an earlier message re virtual directories
that ultimately I want to put it in its own section,
but I wasn't sure that adding to the general configuration syntax was the
right thing to do at this point.
Presumably though this doesn't require another field in #arg at all - it
should be possible to do this by loading the vdir config information into
#sconf
One reason I haven't defined a 'proper' configuration syntax for vdirs yet
is that I'm not sure yet of what this syntax should ultimately be.
Indeed, It may be that vdirs shouldn't be a completely separate item in the
conf, as it may be better described as an attribute of a more general
'directory' or 'location' concept.
Please see also my message to come regarding Yaws-2.0 and config file
format.
>
> One more .. nag, The vdir stuff is really useful but I think it's non
> trivial
> to configure and ... worse to trouble shoot. So please make an effort at
> documenting vdirs.
Ok.. I'll get something in place soon.
Cheers,
Julian
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
