The comment was made during a debate on a new bill which would outlaw religious hatred and the MP in question was trying to make a "witty" point against the bill by claiming to be a Jedi. I don't what's more inane - him thinking he was being funny, or you guys taaking it seriously.
Actually it comes from the Greek daimon (god or spirit) whence the English daemon derives (meaning broadly the same, a supernatural being unseen and unknowable) and hence the *nix daemon meaning something that operates in the background and quietly gets on with the job unseen. The English demon meaning an explicitly evil supernatural being is a fork from the daemon root. Ahem!
MS SQL server has always shipped with it's knickers blowing in the wind. The blank password for sa has been default at least since version 6.0). It is widely known by anyone doing a SQL server install that the first thing you do is change the default password for sa, unfortunately, it all too often gets neglected. Likewise, changing the default port from 1433 and making sure the damn thing isn't connected direct to the Internet (we had a lot of fun on that one in security audits). I used to work as a developer/senior consultant in an MS shop and was horrified by how common it was for people to leave it default (blank password) during development, and then forget to change it when the system went into production or worse find that some schmuck actually coded it in and said "Oh, it'll be too hard to change it now, we'll have to leave it" (bear in mind that sa is kind of the SQL server equivalent of root - think what you'd do to a developer who thought it was OK to have his code run as root with a blank password and then hard-coded it into his code!) This sort of thing is endemic in a lot of MS-based shops - MS don't take security seriously and the "security-as-afterthought" attitude filters down. This is a direct result of what MS think of as "lowering the bar" to programming, but is perhaps better characterised as "Don't worry your fluffy little head about security, we'll take care of that for you (except when we don't)".
But thanks, the story brought back a few nostalgic memories of wide-mouthed clients going all goggle-eyed as we showed them how we'd just connected direct into their new system's database over a dial-up ISP connection;-)
PHP follows the ASP philosophy?!!?? I think you'll find that's the other way round - PHP was out and running web sites while ASP was still "codename Denali"
Tried, loved it (well, as a way of doing COM) - I work in an MS shop where we have a stratgey of ASP at the front making calls to business logic components in COM. Initially had to write loads of VB, then found VJ6 allowed packaging Java code as COM dlls. Just write your code as a Bean, then select COM dll as the output format, tho you also sometimes need to write a COM-specific wrapper to allow for Variants in/out and COM errors. As long as you decouple your business logic code from the COM layer stuff, COM or EJB etc is just a distribution choice - if you do it right, changing ASP-> COM to JSP->Servlet can just be a quick search and replace on the ?SP pages, bung a different wrapper class on the front of the Bean, and off you go. NB, I atcually tend to agree that I'd rather use PHP or JSP->Servlet->EJB than ASP->COM but if you have to use COM, Java is a good and viable choice, and it's often faster and not nearly as nasty as VB
Slashdot Mirror
The comment was made during a debate on a new bill which would outlaw religious hatred and the MP in question was trying to make a "witty" point against the bill by claiming to be a Jedi. I don't what's more inane - him thinking he was being funny, or you guys taaking it seriously.
Actually it comes from the Greek daimon (god or spirit) whence the English daemon derives (meaning broadly the same, a supernatural being unseen and unknowable) and hence the *nix daemon meaning something that operates in the background and quietly gets on with the job unseen. The English demon meaning an explicitly evil supernatural being is a fork from the daemon root. Ahem!
But thanks, the story brought back a few nostalgic memories of wide-mouthed clients going all goggle-eyed as we showed them how we'd just connected direct into their new system's database over a dial-up ISP connection ;-)
PHP follows the ASP philosophy?!!?? I think you'll find that's the other way round - PHP was out and running web sites while ASP was still "codename Denali"
Tried, loved it (well, as a way of doing COM) - I work in an MS shop where we have a stratgey of ASP at the front making calls to business logic components in COM. Initially had to write loads of VB, then found VJ6 allowed packaging Java code as COM dlls. Just write your code as a Bean, then select COM dll as the output format, tho you also sometimes need to write a COM-specific wrapper to allow for Variants in/out and COM errors. As long as you decouple your business logic code from the COM layer stuff, COM or EJB etc is just a distribution choice - if you do it right, changing ASP-> COM to JSP->Servlet can just be a quick search and replace on the ?SP pages, bung a different wrapper class on the front of the Bean, and off you go. NB, I atcually tend to agree that I'd rather use PHP or JSP->Servlet->EJB than ASP->COM but if you have to use COM, Java is a good and viable choice, and it's often faster and not nearly as nasty as VB