Using XML processing typically simplifies a developer’s job–but not when you’re programming in c++. Ever wish someone would create the C++ equivalent of XMLBeans? Someone has. Find out how this new open-source tool fills a serious gap in the C++ software environment.
You May Also Like
Easy fraud detection in Nigerian bank with TouK Nussknacker
- byDominik Przybysz
- September 8, 2017
Problem We have a large mysql database with payment transactions from multiple banks, aggregated for Nigerian biggest operator.…
Spring Security by example: securing methods
- byJakub Nabrdalik
- March 30, 2011
This is a part of a simple Spring Security tutorial:
1. Set up and form authentication
2. User in the backend (getting logged user, authentication, testing)
3. Securing web resources
4. Securing methods
5. OpenID (login via gmail)
6. OAuth2 (login via Facebook)
7. Writing on Facebook wall with Spring Social
Securing web resources is all nice and cool, but in a well designed application it's more natural to secure methods (for example on backend facade or even domain objects). While we may get away with role-based authorization in many intranet business applications, nobody will ever handle assigning roles to users in a public, free to use Internet service. We need authorization based on rules described in our domain.
For example: there is a service AlterStory, that allows cooperative writing of stories, where one user is a director (like a movie director), deciding which chapter proposed by other authors should make it to the final story.
The method for accepting chapters, looks like this:
Read more » 1. Set up and form authentication
2. User in the backend (getting logged user, authentication, testing)
3. Securing web resources
4. Securing methods
5. OpenID (login via gmail)
6. OAuth2 (login via Facebook)
7. Writing on Facebook wall with Spring Social
Securing web resources is all nice and cool, but in a well designed application it's more natural to secure methods (for example on backend facade or even domain objects). While we may get away with role-based authorization in many intranet business applications, nobody will ever handle assigning roles to users in a public, free to use Internet service. We need authorization based on rules described in our domain.
For example: there is a service AlterStory, that allows cooperative writing of stories, where one user is a director (like a movie director), deciding which chapter proposed by other authors should make it to the final story.
The method for accepting chapters, looks like this:
The experience of developing “Quak” during a hackathon.
- byRobert Piwowarek
- May 22, 2019
In March 2019 we held a 2-day hackathon named “Ship IT!” in TouK. I was part of the…