Re: Terminal server
- From: "Will Pearson" <will-pearson@xxxxxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Sun, 16 Jan 2005 19:10:35 -0000
Hi Matthew,
Thanks for that information. It would seem wise to have the server
components take authorisation from the client. There may be multiple
versions of JAWS, all with access to the same server. However, some may not
be authorised for remote client access, something that will be detected if
the client is checked for authorisation.
Hopefully, with the growing trend in the I.T. industry being towards web
services and service orientated architecture in general, at least according
to Pat Helland (see his video at http://channel 9.msdn.com or
http://msdn.microsoft.com/architecture), we won't need thin client solutions
for much longer. The main reason for choosing a thin client solution within
enterprises is central control of the software, thus reducing the time to
upgrade and maintain the software. This can all be eliminated by
distributed component architectures, such as .Net web services, DCOM or
J2EE, which all for auto-updating to be built in and also for dynamic
interfaces that change to suit the needs of the user. If anyone's
interested in an introduction to this, then there's a chapter of "The
Encyclopedia of Humand Computer Interaction", which comes out later this
year, on the subject. Simon Polovina (http://www.polovina.me.uk) and myself
co-authored it, and the book is being published by Ideas Group.
Will
----- Original Message -----
From: "Horspool, Matthew F." <drjaws@xxxxxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Saturday, January 15, 2005 1:21 PM
Subject: RE: Terminal server
> Hi will,
>
> I took most of that info from Eric Damery's What's New recording. It's =
> in
> DAISY format now at
> ftp://ftp.freedomscientific.com/users/hj/private/WebFiles/daisy/Whats_New=
> .zi
> p
> But be warned, it's about 68MB!
>
> Eric said that the authorization would be taken from the client machine
> connected, so you don't need a key on the server. I can't imagine it =
> will
> hurt having the authorization key on the server and the client, but the
> information said it was not a requirement for the server. I'm not =
> entirely
> sure on anything else...
>
> Matthew
>
> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On =
> Behalf
> Of Will Pearson
> Sent: 15 January 2005 12:30
> To: jfw@xxxxxxxxxxxxx
> Subject: Re: Terminal server
>
>
> "Matthew Horspool" wrote:
> <snip>
>
> > * JAWS must be loaded on the Client and the Server.
> >
> > * JAWS must be authorized for Remote Access on the client machine=20
> > (not necessarily the server)
>
> WP: Does this mean that should you not authorise you will have to run =
> JAWS
> in "40 minute mode" on the server? Noting that a reboot is needed to =
> reset
> this timed evaluation period. If so, I cannot see very many network =
> admins
> being overly happy at having to reboot their servers every 40 minutes =
> and
> taking down the network and all other users connected to that network at =
> the
> same time.
>
> Will
>
>
> --
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> To unsubscribe from this mailing list, send a message to
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> Archives located at: //www.freelists.org/archives/jfw
>
> If you have any concerns about the list, post received from the list, or =
> the
> way the list is being run, do not post them to the list. Rather contact =
> the
> list owner at jfw-admins@xxxxxxxxxxxxxx
>
>
>
> --
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> Archives located at: //www.freelists.org/archives/jfw
>
> If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list. Rather contact
the list owner at jfw-admins@xxxxxxxxxxxxxx
>
--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw
If you have any concerns about the list, post received from the list, or the
way the list is being run, do not post them to the list. Rather contact the
list owner at jfw-admins@xxxxxxxxxxxxxx
Other related posts:
