I think it's quite difficult to promise a stable or backward-compatible API/ABI without significantly rewrite the current API. MS will just keep adding new feature in the future and every time we implement a new feature it will be easily break the compatibility.
To provide an ideal API/ABI compatibility we need to rewrite the API and eliminate accessing structs directly (rdpSet specifically), but provide freerdp_get/set functions to access them. This is quite common in modern libraries. However this also adds a small overhead, so it's really a matter of whether it worth the effort. Vic On 03/09/2011 08:31 PM, Otavio Salvador wrote: > I do think we ought to think seriously about it all and be > conservatibe about adding new libraries specially because we do need > to do a better job regarding maintaining ABI/API and handling sonames. > We have vendors (distributions) relying on it now. > ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
