Re: [Erlyaws-list] ssi/yssi relative paths

[jla415 <jl...@gm...>]

Jim Menard wrote:
> 
> On 6/10/07, Claes Wikstrom <kl...@ta...> wrote:
>> ejo...@ya... wrote:
>> > I noticed that File paths work differently between ssi
>> > and yssi.
>> >
>> > i.e.:
>> >
>> > out(Arg)->{ssi,"testdir/ssi_inc.yaws","%",[]}.
>> >
>> > will find the file relative to the yaws docroot.
>> >
>> > But,
>> >
>> > out(Arg)->{yssi,"testdir/ssi_inc.yaws"}.
>> >
>> > will find it relative to the calling yaws file.
>> >
>> > Is there a reason that the file lookups work
>> > differently?
>> >
>>
>> sloppyness ... would be the reason. This cannot be changed though
>> since a change would break code. Should be documented though.
> 
> I'd like to suggest that this is the wrong approach. Now is the time
> to fix this problem. Erlang is getting a lot of press right now, and
> this should be fixed before it's too late. Too late because there will
> hopefully be a lot more users of Erlang and Yaws, and too late because
> an inconsistency like this looks bad.
> 
> 

I'd have to agree here.  It makes little sense to have a relative path ssi
call use the docroot rather than the path to the current file that is
evaluating the ssi call.  Better to fix this now before yaws gets more
adoption as the current user base is well equiped to fix any incompatibilies
during an ugprade with a simple grep and replacement.


-- 
View this message in context: http://www.nabble.com/ssi-yssi-relative-paths-tf3896432.html#a11053530
Sent from the Yaws mailing list archive at Nabble.com.