Studio Fat Window to Web Client Window App

[Stephen Miller]

Please do Sven..

" If you want to I can send to you off list the example that I use at  
Euromnis lecturing - that might give you some insights on how one can  
Work with solutions that will work across different deployment modes."

Brian

Citrix is brilliant - there is no doubt about that but there certainly
are issues with printing support and the general cost. (Of course if you
get enough licenses it is cheap - I have heard of some sites paying $150
a connection).

One of the problems with Citrix though is the total cost of getting ALL
the applications used onto the system. Typically sites start with a list
of 2-3 applications and then end up with many multiples of this for
users who need half a dozen Microsoft apps and scientific calculators,
special text editors etc. Especially with MS apps we are talking about a
serious amount of memory required per connection. 

Michael's new web-client version of his word processor may be very
valuable to some sites in this regard.

Another very interesting solution is the old Tarantella product -
rebadged and developed by Sun as their Secure Desktop. Cheap and
performance is good. 

Maybe this is worth considering Brian?

Regards



Stephen Miller 	
Subject: Re: Studio Fat Window to Web Client Window App

Hi Brian,

As far as I can see it mainly depends on the degree of objectification  
in your app, especially the data management. I do not think that one  
can perform an automatic conversion and get a good, fast and secure  
web client app corresponding in functionality to a client-server  
version. The best approach if one can afford it is to rebuild from the  
beginning.

If you want to I can send to you off list the example that I use at  
Euromnis lecturing - that might give you some insights on how one can  
work with solutions that will work across different deployment modes.

Take care,

Stene

___

21 apr 2009 kl. 17.33 skrev Brian O'Sullivan:

> Also curious of others' experience in migrating thick Omnis  
> applications to the Omnis web-client paradigm - an option I've been  
> asked to evaluate for our applications at DuPont, not on technical  
> merits, but rather as cost-avoidance. At present we host our thick- 
> client apps from a Citrix farm, and we're hosting that on Win2003  
> servers, which will soon go unsupported, and Microsoft exacts a not  
> insignificant license fee to upgrade to the next supported server  
> OS. So we either pay MS lots of money to maintain the current level  
> of functionality, or invest time/$$ into web-client. My gut reaction  
> was that we'd spend more $$ in programming time to adapt the thick  
> apps for web-client, but if there is an automated tool to do the  
> grunt work of creating web-forms, that may make the option more  
> feasible. Of course there are other architectural considerations, as  
> well as coming up to speed with the web-client functionality and  
> limitations vs. thick-client GUI controls, etc. Opinions?
>
> -----------------------------------
> Brian O'Sullivan; Bear, DE
_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________