Reputation
1,189
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
6 18
Impact
~36k people reached

Feb
5
awarded  Popular Question
Jan
27
comment What's the point of running unit tests on a CI server?
@BoristheSpider that workflow sounds great, I assume conflicts still are resolved manually, or is it required for the feature branch to pull master first?
Jan
25
comment Should we avoid language features that C++ has but Java doesn't to increase maintainability?
How are languages to evolve if people are unwilling to use new features? The purpose of the new features is to make your life easier by solving common problems. If users do not use new features, then there's no motivation for anyone to implement them.
Jan
21
awarded  Benefactor
Jan
13
comment Function to return a string - Which is cleaner?
I prefer the second, less variables, return early, all good! It would be better if you passed in the status code instead too, and renamed the method accordingly.
Jan
13
awarded  Promoter
Jan
10
comment Filtering request and responses in RESTful MEAN stack
This is a good point for this particular use case, however I find myself in the same scenario for other resources, for example employee with a field salary.
Jan
10
revised Filtering request and responses in RESTful MEAN stack
edited tags
Jan
10
revised Filtering request and responses in RESTful MEAN stack
edited tags
Jan
10
asked Filtering request and responses in RESTful MEAN stack
Dec
28
comment Tracking online users with a stateless architecture
I guess I don't understand the question, why should the client be transmitted recentUserAccessTimestamp? To me it seems like you're just transferring that state information to the client. If the client sends the old token again, is the system going to behave differently than if it were to send the newer token?
Dec
28
comment Tracking online users with a stateless architecture
I think we may have the same view, just worded differently. In either case, I think it would be worth while to simply store this information server side in the database in some sort of logging / audit table. Just because your application may be saving this information doesn't mean the exposed service has to behave differently because of it.
Dec
28
comment Tracking online users with a stateless architecture
That is different than what most people would consider a stateless service. Stateless typically implies that no state information is passed between client and server. If the server wants to cache things, then that would be opaque to the client.
Dec
28
comment Tracking online users with a stateless architecture
Would this not then make it stateful?
Nov
7
revised How is spinlock different from polling?
Expanding acryonyms
Nov
7
suggested approved edit on How is spinlock different from polling?
Sep
25
comment How should I pass login data from client to server using REST API
Show me the money!
Sep
25
answered How should I pass login data from client to server using REST API
Sep
25
comment How should I pass login data from client to server using REST API
It's bad because it makes it more difficult for the client (they must make an extra call and save state [the token] on their end), and you have to deal with session expiry scenarios on both ends. Stateless restful services are easier to test and understand. I would just pass the authentication information on every call. I do it through headers, I tend to use "basic http authentication", it's a very simple mechanism.
Sep
25
comment How should I pass login data from client to server using REST API
Are you using a session to store persistent state information, or just for authentication? I think it's a good idea to avoid the notion of "sessions" in a restful API, and just pass authentication parameters by header.