On 03/17/2011 03:19 AM, Marc-André Moreau wrote: > > There is also some stuff that should probably be moved out of > libfreerdp. We could make the following modules: > > auth: credssp, ntlmssp, and eventually kerberos. > crypto: all the crypto_, tls_, and secure.c.
Please, let us be pragmatic. There is no need to create separate libraries with public APIs for everything. We can do modularisation without creating separate libraries for each "module". It has some relevance to split optional functionality out in libraries so the dependencies (to for example pulseaudio and cups) are optional. As a consequence of that we might need some common shared utils. Going beyond that will in my opinion have a maintenance overhead but no benefit. I think it is fine to have the choice of crypto backend as compile time option. If somebody some day see a use case for using your credssp/ntlm/nla stuff in another project it can be made a separate library - that probably no longer should be a part of libfreerdp. There is no need to focus on that now. /Mads ------------------------------------------------------------------------------ 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
