Reputation
391
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 5 14
Impact
~19k people reached

  • 0 posts edited
  • 0 helpful flags
  • 27 votes cast
Mar
30
awarded  Good Question
Mar
22
awarded  Famous Question
Dec
1
comment Redistributing Nuget References w/ Licenses
Thank you so much for help reading this. I found myself confused when trying to understand the difference between modifications to the library and the library itself.
Dec
1
accepted Redistributing Nuget References w/ Licenses
Dec
1
comment Redistributing Nuget References w/ Licenses
I can "copy, modify and distribute the covered software in source and/or binary forms". And also "exercise patent rights that would normally only extend to the licensor provided that: all copies, modified or unmodified, are accompanied by a copy of the licence." I am not trying to claim patent rights though. So I don't think I need to copy the license.
Dec
1
asked Redistributing Nuget References w/ Licenses
Nov
30
awarded  Notable Question
Sep
24
awarded  Autobiographer
Aug
4
awarded  Notable Question
Jul
2
awarded  Curious
Apr
28
awarded  Popular Question
Mar
7
awarded  Popular Question
Mar
5
awarded  Nice Question
Dec
24
awarded  Popular Question
Aug
23
awarded  Commentator
Aug
23
accepted Achieving Zero Downtime Deployment
Jun
25
comment Achieving Zero Downtime Deployment
Thanks Joachim ... I like to talk in absolutes so that the basic idea is clear - but you are correct, we could have a policy of being backward compatible by N releases, at which point we can remove unnecessary DB objects.
Jun
24
asked Achieving Zero Downtime Deployment
Mar
11
accepted NoSQL Document Database as a Message Queue
Mar
8
comment NoSQL Document Database as a Message Queue
The aversion currently is: I would like to pull messages off of the queue in some intelligent fashion - not just whatever is next (I know - that's the point of a "queue"). I was thinking of taking them off the traditional "queue", putting them in some DB, and then polling that DB to intelligently get the "next" message to process.