[Seaside] WAFileLibrary / Resource Path

[Philippe Marschall]

2007/8/14, Sebastian Sastre <ssastre at seaswork.com>:
> Hi Ken,
>
>         maybe is too KISS but I've made this a couple of hours ago because I
> didn't want to manage files manually too much. So with this an image is able
> to write in disk all the libraries that a seaside app uses writed in a
> consistent shape under your image dir.
>
>         I'll use rewrite rules in apache so copying that file directory path
> should be enough I think. Maybe you find a way to copy that to S3 and make
> your apps work in deployment/development by making behave differently in
> #updateRoot: ? Could be "the switch" you asked for?
>
>         Be warned: I'm testing it just now myself so.. no guarantees ;)

I added it to Seaside2.8a1-pmm.435 with the usual
SeasidePlatformsupportfication (two more methods :(, where is this
gonna end?). I didn't add #refreshResources. The main problem here is
that people might use it to deploy resources. This kinda sounds like a
joke but WAFileLibrary is not suited for this. Problem is that it
hideously bloats the source size for binary files. An other is that
serving big files over Seaside is not recommended and we can't tell
you where the limit is to the size of files Seaside can serve.
Deployment of resources is an issue that needs to be solved at the
Smalltalk or version control level.

Cheers
Philippe

> Sebastian Sastre
>
>
>
> > -----Mensaje original-----
> > De: seaside-bounces at lists.squeakfoundation.org
> > [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> > de Ken Treis
> > Enviado el: Jueves, 02 de Agosto de 2007 16:21
> > Para: Seaside - general discussion
> > Asunto: [Seaside] WAFileLibrary / Resource Path
> >
> > I'm using Amazon S3 to host my static content, which is easy
> > enough to do using methods like WAImageTag>>resourceUrl:. But
> > the content of the various file libraries is static too, so
> > it seems like it'd make sense to host it on S3 as well.
> >
> > The problem I'm having is that the URLs of file library
> > content isn't relative to the resource base -- so it always
> > looks for /seaside/ files/SULibrary/effects.js, where I'd
> > really prefer something like:
> >
> >       http://mybucket.amazonaws.com/SULibrary/effects.js
> >
> > or
> >
> >       http://s3.amazonaws.com/myBucket/SULibary/effects.js
> >
> > What would be the best way to refactor the code to accomplish this?
> > If nobody's interested in this sort of feature, then I guess
> > I can hack it however I want. But if other people are
> > interested, I'd like to know how to make it as useful as possible.
> >
> > It seems like this behavior should be configurable. Should I
> > just make it use the resource base URL, or keep a separate
> > base URL for files?
> >
> > --
> > Ken Treis
> > Miriam Technologies, Inc.
> >
> > _______________________________________________
> > Seaside mailing list
> > Seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>