Tomáš Chaloupka

I've made the proposed changes. Sorry for the delay - time flies..

What about for example some nullable field from the DB? I'll do the ignore attribute same way after this will be decided which way to go. Also I don't like...

I've added possibility to set direction also to IgnoreAttribute.

@s-ludwig so now it is: * `@optional!InOut` stays `@optional` * `@ignore!InOut` stays `@ignore` * `@optional!Out` and `@ignore!Out` goes away as not needed * `@optional!In` became `@lean` But what about `@ignore!In`?...

And what about leaving `@optional` and `@ignore` without specialization as it was and then introduce for example `@serializePolicy` and `@deserializePolicy` to the REST/web interfaces and use them to fine tune...

@s-ludwig we need a consensus here to move forward :)

rebased and fixed some errors in untested cases

Yeah I figured ;-) So this should probably be fixed with: * fix the SyslogLogger to use "sync queue" approach * warning in the Logger docs for custom loggers that...