-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
as I have indicated on a number of occasions I totally don't get this desire to Java-fy everything. I would like to keep the 'core' DeviceMap code as 'clean' as possible. By that I mean -- this also, in answer to Reza's earlier question on how I see the future : - - zero dependencies - - CLI compliant [.Net specific] - - as platform/language agnostic as possible - - as accurate, fast and small as possible so it can be embedded, dropped, integrated into any other application with zero effort. [Basically, as it is now.] In that scenario I imagine DeviceMap 'core' in for example : - - a canonical DDR compliant client - - a web service - - a client targeting specific user-agent types [bot, OS, version] - - a 'vanilla' MVC client - - a log analysis tool - - ... [I once 'embedded' an Java DeviceMap client in a Tomcat server.] They each have their own specifics with regard to environment, logging etc and the core should neither impose limits nor add a burden to that. I agree that DeviceMap should provide examples of such clients and encourage the development of them but these can only thrive if we : a) keep the 'core' clean and lean [and yes, a little mean] b) work on the data ! ;) esjr -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJVQhYnAAoJEOxywXcFLKYcPQMH+gIdDSugTuGA2aydiP9qEick ffPir6SRSXDTi3qHzkrlG2j2m+fHfUt1F0tSCaCgjt2M3scpnKt9u2vp/vXF1n96 TuJMlXadl38+WU5075uS98Hh0C/ZYpIUHIs3Xn/QzuTR/5SoOSVqiKFO9PZIKDYb fZyIgoP9C4BbyqzKSveoARaSdF8GnV2U977AKSGr1ENpfClxLuB8tIBokQ/lqrGs /xxnTXR8YdO7kU5r2KZhKYhT4e4wT8bH0TubRrO6Pkm7nEZS++cPMVCC/5/c1LHl VQaEUZaVpr6y+3DUsRxvKIqWTGXkl+Olj8hxyV3QJgRk69BVDP+RE3rxd3Pa1Tc= =+fgg -----END PGP SIGNATURE-----
