When the hell will all those people just curl up and die? I'm so heartily sick of that mustachioed hippie free-love deviant ESR spouting his OSS filth. When will he realise that he's made all the money he possibly can from it, and it's time to just shut up and move along now?
S:Are there any other weaknesses to keep in mind, particularly when accessing data on the Web? JS: This gets into engineering implementations. The devil is in the details. Let me give you an example. There's a Web site out there--I won't identify them--that offers survey services. You can set up surveys and revisit them to see the data collected or to edit them. But if you look closely at the actual URL in the little bar at the top of your browser, you will see some long number.
A few of us wanted to know, "Well, wonder what happens if we go into that title bar there where the URL is and just add one to that number?" And we did so, and all of a sudden we were looking at somebody else's survey, and seeing their answers. The devil is in the details.
Yup. Each HTTP request needs to be checked separately for privilege violations. Not doing so is like opening your internal API to anyone who wants to call it... next thing you know, someone is injecting SQL and your database is executing a "DROP TABLE users". Yikes.
Would that we could... but it's running an unstable document management app on there and we're all afraid to mess with it. Argh... there's one of those in every server farm I bet...
> I work for a defense contractor and > we are mostly a Linux shop.
Same here. I'm admin'ing a couple of servers for UltraLog... all running Linux. There's one Solaris box hanging on by its fingernails, but hopefully that'll go away soon too.
Actually, that command is a bad way to do this type of check, since if wget finds an index.html file in the current directory it'll put the HTTP response in "index.html.1". So if you're running the command multiple times, make sure you delete the previously created index.html.
There's some way to do it without writing a file... I can't remember how, though...
Here ya go.
> probably the biggest single improvement
> in testing in twenty years
Right on. Being able to make some changes and run a suite of 500+ tests to make sure things still work is a thing of beauty.
And when a bug slips through, that's just an opportunity to write another test and make sure that bug never happens again. Good stuff.
...in Bret Pettichord's Scripting for Testers one day class.
It talks about eliminating some of the tediousness from testing web applications, mainly by using automated solutions like WTR.
He's also got a list of testing resources that's got some good stuff in there...
Note that the BileBlog has many, many vicious postings on various Java and open source topics - Maven, XDoclet, "J3EE", etc.
In some cases, though, as they say - "it only hurts because it's true".
> comments in a code
Except for good variable/class/method names. Folks, don't bother with Javadoc like:Instead, spend your time giving your methods good names. And, please, refactor a method once its cyclomatic complexity number gets over 10 or so.
...check out SemWebCentral, which is a GForge installation hosting a fair number of Semantic Web-related projects. There's even an OWL mode for Emacs!
And there are also some tutorials and such-like.
> SourceForge
Oops, fixed, thanks!
...you need to have a Terms of Service to deal with junx like this. We've got one on RubyForge just in case...
Hmmm... the CVS repository is empty...
...right here. And here, too.
And lots of other folks contribute too. Good times!
...right here.
Or, if you're on the other end, you can also apply for a used computer.
> Oh, for Guinness sake
Nicely done.
...although, as the announcement says, "Most things seem to be working but there are still some problems with IDE & the framebuffer."
Wired has an article on this, too.
The Guinness of sake, maybe?
...with Ruby-DOOM.
On the other hand, generating a WAD file from a bitmap was tricky enough... ack.
> Just install linux on it :0)
Would that we could... but it's running an unstable document management app on there and we're all afraid to mess with it. Argh... there's one of those in every server farm I bet...
> I work for a defense contractor and
> we are mostly a Linux shop.
Same here. I'm admin'ing a couple of servers for UltraLog... all running Linux. There's one Solaris box hanging on by its fingernails, but hopefully that'll go away soon too.
....right here.
Some cool speakers will be there - Dennis Sosnoski (various Java stuff), Rasmus Lerdorf (PHP).
> OSVBD?
Argh...
s/VB/V/g
...per the database info page.
<shameless>
Hey OSVBD folks, here's a little utility to do do some PostgreSQL query analysis!
</shameless>
...will be taxed for building houses for free.
As a member of the Union of Concerned Carpenters, I applaud this new policy.
Actually, that command is a bad way to do this type of check, since if wget finds an index.html file in the current directory it'll put the HTTP response in "index.html.1". So if you're running the command multiple times, make sure you delete the previously created index.html.
There's some way to do it without writing a file... I can't remember how, though...