Happy Birthday Massimo!
BTW, I've started some work originally based on 'terminal' by
Pritpal, when I was doing it we didn't have a C level socket
API, so I started with a GTUSER GT with .prg callbacks. The
overall idea is indeed quite straightforwards but the devil
is in the details and quality implementation (the tricky bits
are printing / remote app launching and file transfer).
Honestly I couldn't present any meaningful results yet, but
I haven't given up. I'd need some continuous time for
concentration (which apparently comes very rarely). Surely
some ideas / code can even be used from hbnetio.
Brgds,
Viktor
On 2009 Oct 5, at 14:07, Massimo Belgrano wrote:
Thanks
your vision will extend life of harbour application
Today is my birthday and your vision is the best present
gtnet will be a important solution for many user here
how gtnet in windows will recognise user at login to reestablish his
session?
2009/10/5 Przemyslaw Czerpak <dru...@acn.waw.pl>:
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
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
--
Massimo Belgrano
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
