> This is were I fear about the layer. I do like the idea and think this > is the way to go but from our tests here FreeRDP is slower then > RDesktop in some cases and seems to be related to our "indirection" > layer. Adding GDI above it could make it worse.
Yea, bsops.c later libfreerdpgdi was intended for UIs that don't have the minimum set of drawing capabilities RDP needs, like DirectFB and WinCE. The reason the win32redesktop was using bsops.c was because was a win32/wince client. When drawing everything this way you don't use any hardware acceleration. That can be bad on slower thin clients. When I was looking at our new wfreerdp, it looks like it's win32 only. If that is the case, it can be greatly optimized and the drawing issues fixed. If the goal is to be win32/wince compatible, we should use libfreerdpgdi. Jay ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
