Why desktop application can’t be integrated in server-side?However, what if we need such the same thing, but as a web service running in server-side for massive users, it would be tricky and even impossible to implement, because desktop applications are not suitable to run in server environment for two reasons.

Memory leaks, and blue screen.Next, even if web servers could offer desktop environment for each client, it’s highly possible that desktop applications couldn’t get 100% of the resource back to the system. We call it, “Memory Leak”. It’s due to difference between desktop and server environment. Desktop application can be used if it has a small memory leak, because a user will finally shut down the computer. In server-side, however, application should be run repetitively for long period of time. Applications won’t return the same resource that they got from OS, and eventually OS will be out of resource for memory leak. For instance, if one application has 0.01% of memory leak not returning 0.01% of system resource every run, it will cause out of resource when it runs 10,000 times. (We use to have “blue screen” when we have such situation in Windows) In server environment, memory leak is critical for stability and durability of the service.