Using WAFileLibrary for external resources?

All,

as far as I remember WAFileLibrary is not intended to be used in
production. But what's the way "replace" WAFileLibrary  for external use?

I'm currently thinking of patching WAFileLibrary to return external URLs
(i.e. simply using a different #basePath). This would allow me to export
all the files from the file library and simply upload them to the
external URL. By patching the basePath I would not have to touch each
and every reference to the library by hand. Instead something like
"MyWAFileLibrary  / #myFilePng" would simply return an external URL.

Or maybe something like this is already in the image with me being to
dumb to find it :-)

CU,

Udo

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Seaside elements that support #url: also support #resourceUrl: and you
can adjust the base resourse url in preferences of your application
using,

myApp preferenceAt: #resourceBaseUrl put: 'http://mycdn.com/files/'

Hope this helps,

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message header.
Unless otherwise indicated, it contains information that is private and
confidential. If you have received it in error, please notify the sender
and delete the entire message including any attachments.

Thank you.
-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Udo
Schneider
Sent: Thursday, January 08, 2009 12:12 PM
To: [hidden email]
Subject: [Seaside] Using WAFileLibrary for external resources?

All,

as far as I remember WAFileLibrary is not intended to be used in
production. But what's the way "replace" WAFileLibrary  for external
use?

I'm currently thinking of patching WAFileLibrary to return external URLs
(i.e. simply using a different #basePath). This would allow me to export
all the files from the file library and simply upload them to the
external URL. By patching the basePath I would not have to touch each
and every reference to the library by hand. Instead something like
"MyWAFileLibrary  / #myFilePng" would simply return an external URL.

Or maybe something like this is already in the image with me being to
dumb to find it :-)

CU,

Udo

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Boris Popov schrieb:
> Seaside elements that support #url: also support #resourceUrl: and you
> can adjust the base resourse url in preferences of your application
> using,
>
> myApp preferenceAt: #resourceBaseUrl put: 'http://mycdn.com/files/'
Doesn't this not only change the base url of the application and all
it's resources?

I was thinking of hosting the app on something like
http://myapp.mydomain.de/ using your approach above. But most of the
stuff encoded in WAFileLibraries (including such small things like SU)
should be hosted on S3:
http://mypap.s3.amazonaws.com/

Or did I get you totally wrong?

CU,

Udo

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I've used this successfully to do just that by publishing all resources
to S3 for deployment and changing base resource URL; it only affects
tags that use #resourceUrl: API and not your application in general.

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message header.
Unless otherwise indicated, it contains information that is private and
confidential. If you have received it in error, please notify the sender
and delete the entire message including any attachments.

Thank you.
-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Udo
Schneider
Sent: Thursday, January 08, 2009 1:33 PM
To: [hidden email]
Subject: [Seaside] Re: Using WAFileLibrary for external resources?

Boris Popov schrieb:
> Seaside elements that support #url: also support #resourceUrl: and you

> can adjust the base resourse url in preferences of your application
> using,
>
> myApp preferenceAt: #resourceBaseUrl put: 'http://mycdn.com/files/'
Doesn't this not only change the base url of the application and all
it's resources?

I was thinking of hosting the app on something like
http://myapp.mydomain.de/ using your approach above. But most of the
stuff encoded in WAFileLibraries (including such small things like SU)
should be hosted on S3:
http://mypap.s3.amazonaws.com/

Or did I get you totally wrong?

CU,

Udo

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Boris Popov wrote:
> I've used this successfully to do just that by publishing all resources
> to S3 for deployment and changing base resource URL; it only affects
> tags that use #resourceUrl: API and not your application in general.
#resourceUrl: - this was the missing piece I did not see. Thanks for
your help.

Do you only host your own resources on S3? I'd like to host things like
SU there as well.

Thanks,

Udo

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I used to dump everything out.

-Boris (via BlackBerry)

----- Original Message -----
From: [hidden email] <[hidden email]>
To: [hidden email] <[hidden email]>
Sent: Sat Jan 10 02:50:10 2009
Subject: [Seaside] Re: Using WAFileLibrary for external resources?

Boris Popov wrote:
> I've used this successfully to do just that by publishing all resources
> to S3 for deployment and changing base resource URL; it only affects
> tags that use #resourceUrl: API and not your application in general.
#resourceUrl: - this was the missing piece I did not see. Thanks for
your help.

Do you only host your own resources on S3? I'd like to host things like
SU there as well.

Thanks,

Udo

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside