developer toolbox » harbour

> On Mon, 05 Oct 2009, Ernad Husremovic wrote:
> >  > >Especially how do you implement client side ?
> > > Switch to Linux :)
> > I am on linux :). But my custumers are not :(
>
> But only your application needs Linux or other *nix like OS
> and your customer can still use the same OS as so far.
> Believe me that I also do not plan to force any OS on client
> computers.

I know, but there is still problem with single PC and small LAN installations
(where file server PC is workstation also)  

Many of our users are in this class.

ispravka gornjeg posta

> I know, but there is still problem with single PC and small LAN
> installations
> (where file server PC is workstation also)

My mistake, problem with single PC instalation is quite meaningless in the context of this discussion :(.
We have DBFCDX RDD + native windows harbour aplication.

ovo je inače originalni odgovor

On Mon, 05 Oct 2009, Ernad Husremovic wrote:

Hi,

> During this discussions, Przemek explained that he has no needs for client
> server RDD:
> ".. In my case whole applications are executed on server side " ?
> Please, can you explain us what is the architecture of your applications ?
> Especially how do you implement client side ?

It's nothing amazing but standard *nix functionality.
My applications are executed remotely on the server side usually
using some terminal emulators.
I wrote my own 'screen' like program which keeps alive applications
executed on the server side even if client station disconnect or
crashes. In such case program is still running and when user login
again he continues his job using the same instance of programs.
If he want then he can start working with the program in the office
then he can close terminal program without logout from my application
and login from home or on next day and continue his work. For users
there is not difference it's WAN or LAN access.
Because pure terminal programs does not give to the remote program
access to all local resources on client side then we are using also
small servers installed on client computers which are controlled
remotely by application on the server so we can share serial or
USB ports, display pictures, access to local printers or drives,
activate some programs on client computer, etc., We usually use
SHH connections with internal tunnels for our client side services.

In the future GTNET should give the same functionality for all
multiprocess platforms (single process platforms like DOS or WinCE
can be only clients) and should contain buildin most important client
side services with support for executing .hrb code sent dynamically
from the server side so programmers can easy extend it in any way he
want also dynamically not only by static relinking client side code.
Now this functionality is available if user collects (in some cases
creates) all peaces himself though it's not very hard work.

best regards,
Przemek

Massimo

----- "Massimo Belgrano" <mbelgrano@deltain.it> wrote:

> You can use Use linux on windows using virual machine
> microsoft,vmware
>
> you can download an Ubuntu 8.04 (Desktop) VMware Image. This virtual
> Linux system with all its applications is usable out-of-the-box (e.g.
> with the free VMware Player)
> http://jars.de/english/ubuntu-804-vmware-image-download-english
>

Thank you Massimo for your suggestion, but we are talking about small budget customers,
with small budget hardware (read low capacity hardware).

That would be easily begin nightmare to maintain.

By the way, We have experience with virtualization tools like vmware, virtualbox.

In your proposed scenario vmware server (free also) or virtualbox would be better match than vmware player.

> 2009/10/5 Ernad Husremovic <hernad@sigma-com.net>:
> >> On Mon, 05 Oct 2009, Ernad Husremovic wrote:
> >> >  > >Especially how do you implement client side ?
> >> > > Switch to Linux :)
> >> > I am on linux :). But my custumers are not :(
> >>
> >> But only your application needs Linux or other *nix like OS
> >> and your customer can still use the same OS as so far.
> >> Believe me that I also do not plan to force any OS on client
> >> computers.
> >
> > I know, but there is still problem with single PC and small LAN
> installations
> > (where file server PC is workstation also)
> >
> > Many of our users are in this class.

Re: [Harbour] What is Przemek's architecture ? Pon 05 Okt 2009 14:31:41

From:     harbour.01@syenar.hu
To:     harbour@harbour-project.org
Reply To:     harbour@harbour-project.org
Sender:     harbour-bounces@harbour-project.org
>> -----Original Message-----
>> From: Ernad Husremovic [mailto:hernad@sigma-com.net]
>> Sent: Monday, October 05, 2009 11:49 AM
>
> ...
>
>> Especially how do you implement client side ?
>
> Switch to Linux :)

Aside from jokes, IMO it'd be much convenient to use our
own thin-client app, than apps like putty. putty has a
hard time handling several key combinations. And it's
usually a PITA to sync it with server side, encoding,
mouse and whatnot. (maybe it's just me, but we certainly
cannot call it a "plug&play" experience).

Hard is now perfectly suited to provide such thin clients
for all important OSes, and the same can be said about the
server-side.

Now Harbour make system makes it easy to integrate OpenSSL
into such GTNET lib, so this is also not such an obstacle
anymore as it was, say a year ago.

Another idea: Given well documented GTNET protocol, client
could even be written in Java, which makes it uber-portable
and even embeddable into webpage.

Brgds,
Viktor