[THIN] Re: .NET and Citrix

  • From: "Connor Durflinger" <cdurflinger@xxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 28 Feb 2003 10:43:10 -0500

The thing about a Web service is that it doesn't have an interface.
It's just an XML data feed.  People are conflating Web-based
applications with Web services.  All a Web service is, is a different
way to implement remote procedure calls.

There are some cases where this will replace Citrix.  Consider an Office
11 Excel spreadsheet that pulls data via a Web service from a back-end
database, versus a thick client published via Citrix pulling data from
the same server.  In some circumstances it will be simpler to deliver
the Excel template to a remote user, rather than giving access to the
entire published application.

On the other hand, even with a Web service you *still* don't have a
zero-touch installation on the remote side.  Someone's got to grab that
webservice and do something with it.  Reall, it's just going to depend
on preferences -- do you want to deploy the architecture to safely
publish your webservice (VPN, encryption, client certificates, software
delivered to the remote user), or do you just want to publish an
application?

Connor Durflinger
Sr. Network Engineer
New England Network Group
cdurflinger@xxxxxxxxxxxx
tel: 781.397.0990  x 18

"Only connect." -- EM Forster


-----Original Message-----
From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx]=20
Sent: Friday, February 28, 2003 10:21 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: .NET and Citrix



But in all fairness, from a bandwidth standpoint, and such, running them
through Citrix would still be more efficient, I would think.

-----Original Message-----
From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx]
Sent: Friday, February 28, 2003 9:17 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: .NET and Citrix



Oh this is true. Web serviced applications WILL in the future, be the
bomb. Of course I have heard that for 4 years now.

And I still see DOS Apps on terminal services and of course how many of
these app vendors (besides MS) are really going to move everything web
based and how soon?

Ron Oglesby
Senior Technical Architect
=3D20
RapidApp
Office 312.372.7188
Mobile 312.961.2380
email roglesby@xxxxxxxxxxxx
=3D20


-----Original Message-----
From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx]=3D20
Sent: Friday, February 28, 2003 9:08 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: .NET and Citrix



Good information, but I have people looking at it more from, "once we go
web-services, there will be no need for Citrix, everything will be web
based."

Rephrase, Ron, that is GREAT info.

-----Original Message-----
From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx]
Sent: Friday, February 28, 2003 9:02 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: .NET and Citrix



Lets talk about a few things here. I don't know if anyone else really
has it running but I have it (RC2) in two clients using it both as an MS
only env, and as a MetaFrame platform.=3D3D20

Both locations are using it for some pre-prod stuff right now but there
are some users using it. Limitations and or problems:

1st problem that hits everyone is lack of published app support. Nothing
like it, it pretty much operates as it does now.

2- Licensing model is cool I like that Named user or per device (as it
is now)

3- XP pro clients issued after the release date of 2003 Server will no
longer have a terminal server cal built in. You have to buy it. (Typical
MS pain)

4- MS Load Balancing, Coming on all version now. Only problem is that it
is MS load balancing. It still does not do what a terminal server needs
and look at current number of users logged on or at metrics that really
matter to a Terminal Server.

Of course MS LB'ing is also limited to 32 nodes MAX, and performance
starts to go down above 20

5- If you use a Third Party load Balancer it gets better but still
doesn't Match Citrix.

6- The session directory that is used for reconnecting clients to
disconnected sessions IS cool. But it has two problems. 1- LB'ing routes
users any where it feels like. Once the user is establishing a connect
to a server the session directory is checked. IF they have an open
session then the user basically cut off from that server and then a new
RDP session is established with the original server. Of course this only
happens after the LOGON is done on the first server since it needs your
username and password...... Kinda Clunky if you ask me. The second
problem with this is that you have to have Enterprise to use it.
Standard server will not use the session directory but can host it for
the farm.

8- The RDP client is basically the same one that comes with XP clients
now, and the TSAC has changed very little, Of course with the RDP client
you can save RDP files (if you look at them they look kinda like ICA
files). The problem here is that the Active X control used by the TSAC
wont use an RDP file. I had this wild idea of building RDP files and
creating links to them the way we used to with ICA files.  Still working
on this a bit now.

Ron
=3D3D20



Ron Oglesby
Senior Technical Architect
=3D3D20
RapidApp
Office 312.372.7188
Mobile 312.961.2380
email roglesby@xxxxxxxxxxxx
=3D3D20


-----Original Message-----
From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx]=3D3D20
Sent: Thursday, February 27, 2003 4:11 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] .NET and Citrix



I need some help.

I have people here beginning to discuss .NET quite heavily and how we
won't need Citrix, once we go to .NET web based apps., etc.

I have heard people talk about how Citrix will compliment those apps.
Any input?

Chad M. Schneider
Technology Analyst II
Curwood, Inc.
920-303-7609 - Office
920-909-7609 - Pager


*********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for Citrix
Metaframe and Microsoft Terminal Services! http://www.thinprint.com
**********************************************************

For Archives, to Unsubscribe, Subscribe or=3D3D20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
*********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for Citrix
Metaframe and Microsoft Terminal Services! http://www.thinprint.com
**********************************************************

For Archives, to Unsubscribe, Subscribe or=3D20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm

*********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for Citrix
Metaframe and Microsoft Terminal Services! http://www.thinprint.com
**********************************************************

For Archives, to Unsubscribe, Subscribe or=3D20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
*********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for Citrix
Metaframe and Microsoft Terminal Services! http://www.thinprint.com
**********************************************************

For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm

*********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for Citrix
Metaframe and Microsoft Terminal Services! http://www.thinprint.com
**********************************************************

For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
*********************************************************
This Week's Sponsor - ThinPrint
Simply the best print solution for Citrix
Metaframe and Microsoft Terminal Services!
http://www.thinprint.com
**********************************************************

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm

Other related posts: