Top 10 security vulnerabilities:
https://www.owasp.org/index.php/Top_10_2010Tools for implementing secure web applications:
Thursday, July 28, 2011
Tuesday, March 29, 2011
Thursday, January 27, 2011
Nginx web server with a Varnish cache
Nginx is a new breed of web server that scales to massive numbers of connections without running into memory problems. It does this by taking advantage of operating system services for tasks and by keeping things simple (lack of fancy services). Stand aside Apache!
Varnish provides caching with simple configuration, with the ability to get specific about what to cache. And, curiously, you can place it in front of and/or behind the worker server. (Does not handle HTTPS.)
Love simple technology solutions.
Varnish provides caching with simple configuration, with the ability to get specific about what to cache. And, curiously, you can place it in front of and/or behind the worker server. (Does not handle HTTPS.)
Love simple technology solutions.
Friday, July 2, 2010
Bordello - Poor man's dependency injection
What do you do when there is no Spring or other facility to handle dependency injection? How do you fake services in your unit tests?
One way is to use Bordello to instantiate services in the application code. It is not dependency injection per se but it lets you test.
This is a variation on www.artima.com/weblogs/viewpost.jsp?thread=238562 that handles concurrency correctly.
One way is to use Bordello to instantiate services in the application code. It is not dependency injection per se but it lets you test.
This is a variation on www.artima.com/weblogs/viewpost.jsp?thread=238562 that handles concurrency correctly.
Friday, June 18, 2010
RESTful POST Once Exactly (POE) variation
How do you control form POSTs from the client (browser) to the server to prevent a double-submit from being processed twice on the server?
Client : POST "/widget/" Expect: 100-continue []
Server : write new transaction id to db
Server response : 100 Continue, POE: {tranid}
Client : POST "/widget/" POE: {tranid} [body]
Server : POE {tranid} exist in db?
Server : delete {tranid}
Server : Create new resource from [body].
Server response : 201 Created, Location: {newuri} [body]
Client : ...
Client : POST "/widget/" Expect: 100-continue []
Server : write new transaction id to db
Server response : 100 Continue, POE: {tranid}
Client : POST "/widget/" POE: {tranid} [body]
Server : POE {tranid} exist in db?
Server : delete {tranid}
Server : Create new resource from [body].
Server response : 201 Created, Location: {newuri} [body]
Client : ...
Hibernate Entity equals - id or others
The Hibernate entity object represents a database table and the Java equals(Object o) method determines identity among entities for a given table.
Hibernate itself identifies rows from a table by their primary keys, following the principles of relational theory as developed by Edgar Codd in the 1960s. Today the id is typically generated automatically by Hibernate and the database engine.
A new theory says that an entity's equals method should not compare ids but should compare all attributes other than the id, i.e. value1 and value2 in the example above.
Arguments FOR comparing attributes other than the id
A. Differences would typically be encountered fairly rapidly making the additional processing negligible.
Arguments AGAINST comparing attributes other than the id
Bottom line
The Hibernate entity equals method should compare IDs.
Hibernate itself identifies rows from a table by their primary keys, following the principles of relational theory as developed by Edgar Codd in the 1960s. Today the id is typically generated automatically by Hibernate and the database engine.
A new theory says that an entity's equals method should not compare ids but should compare all attributes other than the id, i.e. value1 and value2 in the example above.
Arguments FOR comparing attributes other than the id
- When creating new entities, the entity has no id assigned before it is saved to database, so the id cannot be used to determine identity.
- It is the various attribute values, not the id, that make up the significance of any row of data.
A. Differences would typically be encountered fairly rapidly making the additional processing negligible.
Arguments AGAINST comparing attributes other than the id
- Hibernate lazy initialization can be triggered by a comparison after the Hibernate session has ended. Scenarios include cached entities.
- Regardless of identical attribute values, if the ids are different then there are separate rows in the database.
- The comparing of ids parallels relational theory, a central principle for all relational databases, also paralleled by Hibernate.
Bottom line
The Hibernate entity equals method should compare IDs.
PHP Love/Hate - Inheritance Depth
Just made the discovery that class inheritance has its limits in PHP. It took several days of pain to discover this, due to the fact that my hosting server (5.1.6) does not run exactly the same version as my dev environment (5.2.5), and the particular transaction I was testing is initiated by PayPal.
Lesson learned:
I guess I'm spoiled my the elegance of Java and Ruby, expect industrial strength engines. And I have to admit I am no virtuoso in my command of PHP.
Hopefully eclipse Galileo's PDT 2.1 (PHP Development Toolkit) might ease my dev pain.
Lesson learned:
- Single inheritance is ok
- > 1 inheritance depth fails in some versions
I guess I'm spoiled my the elegance of Java and Ruby, expect industrial strength engines. And I have to admit I am no virtuoso in my command of PHP.
Hopefully eclipse Galileo's PDT 2.1 (PHP Development Toolkit) might ease my dev pain.
Subscribe to:
Posts (Atom)