Authorization and Authentication are hard. when you only have to implement them once (as you do within a monolith) instead of over and over again, it makes the developer happy :-), and maybe leads to less implementation failures.
When you have a bunch of microservices, this is something that has to be considered.
Implement it once or in every microservice, or something in between?
if your ps3 controller just vibrates when connecting to the retropie, or when your ps3 controller does not connect via bluetooth, this writedown might help you.
Since no exact description did work for me, I decided to write it down, what I did based on other descriptions, in order to get it to work.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
http://git-scm.com/ | |
http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging | |
http://ndpsoftware.com/git-cheatsheet.html | |
https://help.github.com/articles/fork-a-repo | |
git status | |
git clean |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
interface Option { | |
key: string; | |
label: string; | |
} | |
const results = [ | |
{ k: "1", l: 1 }, | |
{ k: "2", l: 2 }, | |
]; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// code from http://stackoverflow.com/questions/29771597/how-can-i-construct-a-template-string-from-a-regular-string | |
// + handling unlimited arguments | |
function assemble(literal, params) { | |
var args = [].slice.apply(arguments) | |
args.shift() | |
return new Function(args, "return `"+literal+"`") | |
} |
thread vs eventloop
or java vs node.js
http://docs.spring.io/spring-data/mongodb/docs/1.5.4.RELEASE/reference/html/mapping-chapter.html
6.3.1 Mapping annotation overview
The MappingMongoConverter can use metadata to drive the mapping of objects to documents. An overview of the annotations is provided below
- @Id - applied at the field level to mark the field used for identiy purpose.
- @Document - applied at the class level to indicate this class is a candidate for mapping to the database. You can specify the name of the collection where the database will be stored. @Document(collection = "collectionName")
- @DBRef - applied at the field to indicate it is to be stored using a com.mongodb.DBRef.
- @Indexed - applied at the field level to describe how to index the field.
NewerOlder