You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@vcl.apache.org by Mike Haudenschild <mi...@longsight.com> on 2012/03/14 12:55:30 UTC

Adding a delay to the Connect button

Afternoon, dev team --

I noticed a jira item roll past my Inbox a week or so back regarding adding
a delay in the code between when the user clicks the "Connect!" button and
when the RDP file is actually available.  I'm experiencing the issue that
the ticket addressed -- if a user is really on it, the RDP connection can
be starting before the target computer is actually ready to receive it.

I'm still running the 2.2.1 release.  Is the fix for this easy enough that
I could just adjust a few lines in the existing code?

Thanks as always,
Mike

--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
mike@longsight.com
www.longsight.com

Re: Adding a delay to the Connect button

Posted by Mike Haudenschild <mi...@longsight.com>.

Thanks, Josh!


On Wed, Mar 14, 2012 at 08:52, Josh Thompson <jo...@ncsu.edu> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mike,
>
> Yes, if you look at the JIRA issue[1], you'll see some code contributed by
> Gerhard Hartl that will work with 2.2.1.
>
> Josh
>
> [1] https://issues.apache.org/jira/browse/VCL-444
>
> On Wednesday, March 14, 2012 7:55:30 AM Mike Haudenschild wrote:
> > Afternoon, dev team --
> >
> > I noticed a jira item roll past my Inbox a week or so back regarding
> adding
> > a delay in the code between when the user clicks the "Connect!" button
> and
> > when the RDP file is actually available.  I'm experiencing the issue that
> > the ticket addressed -- if a user is really on it, the RDP connection can
> > be starting before the target computer is actually ready to receive it.
> >
> > I'm still running the 2.2.1 release.  Is the fix for this easy enough
> that
> > I could just adjust a few lines in the existing code?
> >
> > Thanks as always,
> > Mike
> >
> > --
> > *Mike Haudenschild*
> > Education Systems Manager
> > Longsight Group
> > (740) 599-5005 x809
> > mike@longsight.com
> > www.longsight.com
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
>
> iEYEARECAAYFAk9glKwACgkQV/LQcNdtPQObqgCfdlAIcriASUUOYl5OfvfVC1lJ
> MG8An25XKYxJZI6XUh6x4YUpsKx7EmV1
> =390w
> -----END PGP SIGNATURE-----
>
>

Re: Adding a delay to the Connect button

Posted by Josh Thompson <jo...@ncsu.edu>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike,

Yes, if you look at the JIRA issue[1], you'll see some code contributed by 
Gerhard Hartl that will work with 2.2.1.

Josh

[1] https://issues.apache.org/jira/browse/VCL-444

On Wednesday, March 14, 2012 7:55:30 AM Mike Haudenschild wrote:
> Afternoon, dev team --
> 
> I noticed a jira item roll past my Inbox a week or so back regarding adding
> a delay in the code between when the user clicks the "Connect!" button and
> when the RDP file is actually available.  I'm experiencing the issue that
> the ticket addressed -- if a user is really on it, the RDP connection can
> be starting before the target computer is actually ready to receive it.
> 
> I'm still running the 2.2.1 release.  Is the fix for this easy enough that
> I could just adjust a few lines in the existing code?
> 
> Thanks as always,
> Mike
> 
> --
> *Mike Haudenschild*
> Education Systems Manager
> Longsight Group
> (740) 599-5005 x809
> mike@longsight.com
> www.longsight.com
- -- 
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk9glKwACgkQV/LQcNdtPQObqgCfdlAIcriASUUOYl5OfvfVC1lJ
MG8An25XKYxJZI6XUh6x4YUpsKx7EmV1
=390w
-----END PGP SIGNATURE-----