-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for the flowers :-)
> You're 100% right about that. We have to take precautions to make sure users > of the API do not shoot themselves in the foot. Each case needs to be > analyzed and changes to make some mutable structures immutable must be put > into our roadmap. Well, that may be a hard time to analyze everything. Maybe we can find a pattern to solve this. > > Felix this might be something that might help as an exercise for you to get > to know the internals of the server much better. Right now you're of course > invaluable to us in the way you've picked up various tasks. However you > might find it extremely pleasurable to start tinkering with the more meaty > issues of the server. We have several very interesting problems and > rewarding potential solutions in this architecture. Just talk about them and let others share the ideas (or did I missed some documentation?). In addition, knowing > your insight and strict approach to following conventions, we would always > love to hear your suggestions on these matters as well. Well, all I do for now is analysing generated reports and command line outputs when generating the reports. I'm sure, if I listen long enough to what the application wants to tell I get deeper and deeper into the internals of it ;-) Regards Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvwUcMACgkQ2lZVCB08qHG7JgCgi3ASyH0QAjGkuyMlg7TkhJ4I GOUAoL04U2EmbEodNeZnaMdbpIgN32wC =YWyM -----END PGP SIGNATURE-----
