If hate isn't a crime, why is inciting hatred a crime? This is one question the liberal fascists can't answer. Inciting violence is a crime, because violence is a crime, commissioning a crime is a crime. But hatred?
Liberals, not being people who like taking responsibility for their own actions, like the idea that nebulous things such as "speech" can be held responsible for events. Ergo, punish the speech.
The problem with "inciting hatred" is that it's such a nebulous term that anything can be interpreted in that way by even the most hypersensitive paranoiac and before you know it, you're not saying anything for fear of being arrested. For some people, saying that sodomy is grotesque is enough to merit a penalty.
Britain's Labour government are a sad, sad, desperate, miserable bunch of barrel scraping nation destroyers. We were owed an election years ago.
Keeping your business and presentation layers separate is the key to ensuring that your options are open in future. I'd like to think that I could take my php web app and put it into a php-gtk application without much extra work.
I could see a time when that happens somewhere down the line when the same app is basically offered in web or desktop format. There's definitely a time and a place for desktop apps. The web is a pretty square peg for the round holes of business, though you can get away with a lot.
OK, so, how in SOA would I instantiate a class, use a set method to change a property, call various methods on that class, change the property again, call the same methods again, all within the same block of code, all reusing the same database connection and other resources? Or how would I use one SOA service instance as a method parameter to another service instance and then act upon get and set methods within it?
I've got nothing against RPC per-se, but the idea that it's a panacea or a substitute for proper programming is misleading. It has a potential to be a nightmare, revolving your infrastructure around stateless and crude networked methods, which is all it ever seems to be. It also has the potential to spawn endless apps on endless platforms leading to a management hell further down the line, when what you need to be doing is sharing libraries on the same platform that guarantee efficient use of resources.
Yes, platform neutrality is appealing, but platforms offer huge benefits - user management, auditing, access control, resource management, etc, etc.
We love the idea of the network and the internet because they've brought us so much but the fact is those are sub-optimal paradigms. HTTP is crap. Web applications are a massive compromise of usability versus accessibility. SOAP and RPC enable machines to talk to each other across the wire easily. But be honest, if you didn't have to, why would you choose to?
SOA strikes me as a backwards step for an IT operation, and an excuse for not consolidating and sorting out your infrastructure.
The point of OO is that you can gain the benefits of polymorphism and inheritance, the ability to reuse code and build up a modular and flexible code library. That's why the world has moved away from procedural languages.
SOA is the idea that everything can be reduced to XML being fired backwards and forwards. If it's just access to data that's the issue, use a proper RDBMS. Use views, triggers and stored procedures if you want that data presented to different people in different ways. Use networked clients - after all, most of the time SOA is used within the enterprise, and most of the time enterprises control their software stacks and networks.
SOA - Sort Out your Architecture.
Those who do things in a noble spirit of self-sacrifice are to be avoided at all costs. -- N. Alexander.