Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread  EWB2 Files in different server from Data Server
Fri, Nov 20 2015 12:42 PMPermanent Link

A.Kyr

Hi to all,

I examine the option of keeping all EWB2 files of a big WebAppl (js, html and additional images) in a cheap hosted web site and keep the application and data server in house (also with static ip).
This way i want to save bandwidth as the data traffic will be very light unlike js that will be some 2+ Mb.
So, Is this possible?
If yes, what adjustements i have to do event by hand in js produced file?

If it is already answered already elsewhere then please give me a link.

Thanks in advance

A.Kyriakos
Fri, Nov 20 2015 2:11 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com


<< I examine the option of keeping all EWB2 files of a big WebAppl (js, html and additional images) in a cheap hosted web site and keep the application and data server in house (also with static ip). This way i want to save bandwidth as the data traffic will be very light unlike js that will be some 2+ Mb.  So, Is this possible? >>

Yes.  Will you be using the EWB Web Server in-house, or something else ?  If you'll be using the EWB Web Server, then you'll need to make sure that the "Enable Cross-Origin Resource Sharing" option on the Content page of the configuration dialog is *enabled*:

http://www.elevatesoft.com/manual?action=viewtopic&id=ewb2&topic=Configuring_Server

That will allow the EWB Web Server to handle the cross-origin requests from the host's web server properly.

<< If yes, what adjustements i have to do event by hand in js produced file? >>

They key items are:

1) Any dataset requests must be directed to your web server instead of the host, so Database.BaseURL must be changed at application startup (main form's OnCreate event handler or unit initialization section are both good locations for this code).

2) Any plain server requests must use the URL of your web server instead of the host.

3) Any additional content requests using URLs in TImage, TBrowser, TPlugin, TScript, etc. controls/components must be adjusted as necessary.

These changes are what cause cross-origin requests to occur, thus necessitating the CORS changes in the EWB Web Server settings.

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Nov 20 2015 5:25 PMPermanent Link

A.Kyr

Hi Tim

Thanks for your reply.
I use my custom made appl.server, so i will haven't any problem with cross origin concept
I will try your advice and i needed i will come back for more help.

Thanks

A.Kyr
Image