I am thinking of the following scenario. Please advise if it is a feasible setup.

o   Windows program on a desktop using DBISAM tables and with wifi connection.
o   EWB program running on a web server in the same desktop accessing the same DBISAM tables.
o   User within range of wifi using a browser to access the EWB program to update certain DBISAM tables.
o   User could be using any browser on IOS, Android, Linux or Windows.

Frederick

Yes, all quite feasible. You could get quite fancy, or keep it simple. I wrote a
Delphi application that embeds the Chromium browser so that the end user runs a
normal Windows application but the EWB page is the actual content of the window.
The container auto-adjusts to the EWB page size by examining a hidden label. If you
wanted, this could also actually be the web server and handle the data management,
but then you'd have to have the desktop app open all the time. Or you could have a
service that is running all the time, and the browsers all talk to that.

/Matthew Jones/

On 9/18/2013 11:59 PM, Frederick Chin wrote:
> I am thinking of the following scenario. Please advise if it is a feasible setup.

> o   Windows program on a desktop using DBISAM tables and with wifi connection.

I assume by this you simply want the desktop app to use DBISAM data -
that works just fine as DBISAM is multi-user.


> o   EWB program running on a web server in the same desktop accessing the same DBISAM tables.

You still need something that allows EWB app access to the DBISAM -
easiest route is to just run the EWB Web Server on the desktop machine.

EWB app is served up by the web server (it's just HTML/js/css files) but
runs in the browser of the device and then has to communicate with the
back-end web service for DBISAM access and updates. EWB Web Server can
do all of that out of the box.

> o   User within range of wifi using a browser to access the EWB program to update certain DBISAM tables.
No problem - assuming previous point is resolved (use EWB web server).

> o   User could be using any browser on IOS, Android, Linux or Windows.
Again OK though your EWB app should adjust to smaller screen size if you
use smartphone.

Raul

Thank you for your replies.

Assuming EWB's web server is used, what is the best way to handle the dynamic IP situation and SSL?

Frederick

On 9/20/2013 12:11 AM, Frederick Chin wrote:
> Assuming EWB's web server is used, what is the best way to handle the dynamic IP situation and SSL?

IP aspect is something you need to deal with yourself at this time.

EWB Web server does not yet have SSL capability so you'd have to use
something like stunnel (www.stunnel.org). Are you on public LAN (i.e.
like starbucks/internet cafe) ?

Raul

/*
IP aspect is something you need to deal with yourself at this time.
*/

I think for the dynamic IP, I will have to use one of those dynamic DNS web sites.

/*
EWB Web server does not yet have SSL capability so you'd have to use
something like stunnel (www.stunnel.org). Are you on public LAN (i.e.
like starbucks/internet cafe) ?
*/

Nope, I am not on a public LAN but an office network.

Frederick

If you have a single fixed IP computer, then you could do something clever to have
the dynamic computer register itself (effectively an internal dynamic DNS). Your
client would use the fixed one as a proxy.

I suggest though it would be better to have a service and run it on a fixed IP
internally, and just have the clients remember that.

/Matthew Jones/

>Frederick Chin wrote:
>I think for the dynamic IP, I will have to use one of those dynamic DNS web sites.

Since you're on an office network do they already have a DNS server? If so you just have to make sure the PC (or DHCP server) registers the new IP in there (this is built into windows already)

Then your client devices can simply use the dnsname (i.e. host.domain.com) or even create a CNAME for the app so its app.domain.com.

Raul

/*
Since you're on an office network do they already have a DNS server? If so you just have to make sure the PC (or DHCP server) registers the new IP in there (this is built into windows already)

Then your client devices can simply use the dnsname (i.e. host.domain.com) or even create a CNAME for the app so its app.domain.com.
*/

Thanks for the information. I will definitely do this once the app is completed. So much to learn, so little time.

Frederick

(Matthew Jones) wrote:
/*
If you have a single fixed IP computer, then you could do something clever to have
the dynamic computer register itself (effectively an internal dynamic DNS). Your
client would use the fixed one as a proxy.

I suggest though it would be better to have a service and run it on a fixed IP
internally, and just have the clients remember that.
*/

Thank you for the suggestion. I will explore this as well.

Frederick