On Wed, Nov 11, 2009 at 4:22 AM, oiaohm <wineforum-user@xxxxxxxxxx> wrote: > - has it any technical sense ? > Normally no jpsotta. Wine is not really recommend that kind of operation. > > - can Wine be the interface between the server Linux and the Windows application ? > > Yes and no. Wine not what you call light. Next problem is lot of windows programs require graphical to operate. This means X11 server of some form. So really not light. > > Wine is for running Windows applications not really bridging. It pure running the application server would take responsibility for control. > > - user access would be through a bridge with my web site (Joomla-based) > > You will find access control better handled by native tools. Less overhead. Samba can provide lookups on MS ADS servers. Basically there is no form of secuirty look-up Linux cannot already do natively. > > Even vpn connections there are open source ways of doing them. > > Final one that kills this idea is that Wine does not control the Linux network stack in any way. So cannot force traffic to be redirected to it. > > Simpler to stick to webserver controls. Its far more stable less cpu load and less likely to play up jpsotta. > > http://httpd.apache.org/docs/2.2/howto/auth.html You will find most open source webservers provide secuirty control modules like these. It will do a far better job in stablity than what you are thinking about jpsotta > > > > > >
