Andreas,
Right, "native clients" are strictly binary code, no Java at
all. When it comes to the native clients, be aware that:
- Native clients were basically deprecated in the 4.0 release - that is,
no new development since then, only priority bug fixes. So, the new
client-side performance improvements included in the 4.30 release were
not retrofitted to the native clients; so even if you upgraded the
server to 4.30+, you wouldn't see much, if any, of the performance fixes
that were made.
- The 4.40 release (yesterday's) no longer supports *any* native
client; this isn't simply a "support" issue, the infrastructure that
supported the Classic Webtop and Native Clients has been removed, and so
these client types will not be able to connect to a 4.40 server.
With the "/sgd" or "tcc" client, there's basically two parts of the
client - a Client Helper applet, and a native binary component. The
Client Helper installs and starts the native binary client, as well as
various other "housekeeping" type activities; the native component,
(named the tcc on windows, or ttatcc on other platforms), generally does
all out-of-place windows displays, that is, applications windows which
are not displayed in the web browser. For applications that display
within the web browser (display using = webtop or new browser), then
client-side Java is used.
In any event, if you're using the native client now, then client-side
Java isn't the concern.
ADSL to the client should be plenty, but the bandwidth budget as you get
closer to the server is most often the critical factor - 2 Mbps for a
server connection can go pretty quickly, depending on the number of
users you're trying to accomodate.
You might look at tweaking some of the AIP / user bandwidth settings to
see if that helps, and be sure to remove unnecessary things (like
wallpapers, excessive color depth, window size, etc.) Ultimately,
though, if the latency you mention is network latency, there's only so
much that can be done.
Hope this helps,
Rick
Andreas Höschler wrote:
Hi Rick,
There were significant client display performance improvements
made in the 4.30 release, so an upgrade *may* help.
Are your users using the Java client, or the standard client?
The native client for Mac and Windows downloadable from the SGD
greeting page.
The problems you describe remind me of bugs in client-side Java,
back in the 1.4.2 builds - but you wouldn't see them now unless
your using the Classic Webtop client, or possibly, displaying
application in the browser, which requires Java to do the display.
OK, so you say when downloading the native client for a specific
platform (Mac, Windows,...) then no Java is used on the client side?
The native clients are written in C, C++,...?
Thanks for the info. We will give the latest release a try!
Regards,
Andreas
_______________________________________________
SGD-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sgd-users
--
Rick Butland
E-Mail: [EMAIL PROTECTED]
AccessLine: (703) 579-1947 x53261
Direct: (703) 444-9398
Mobile: (703) 328-8130
_______________________________________________
SGD-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sgd-users
