February 18, 2009 at 11:17 pm (Humor)
Step 0: Write just enough code to actually qualify as an open source project. Maybe a little less.
Step 1: Hack together a project website that’s more about SEO than it is about promoting your project. Don’t forget to mention the Killer Ajax Framework which you developed in 2007.
Step 2: Host your project on SourceForge, and ask the SourceForge administrators to artificially inflate your project’s ranking. Because you rock, and they know it!
Step 3: When the SourceForge admins politely tell you to get lost, take matters into your own hands and artificially inflate your project’s ranking yourself by spamming your own forums. Number 1, baby!
Step 4: Take advantage of TheServerSide’s new and improved RubberStampTM editorial process by submitting an eloquent and compelling introduction to your project.
Step 5: Profit, you crazy diamond!
Update (February 15, 2011): Step 6 apparently involves posting spam to the comment section of snarky blog entries which poke fun at your project in thinly veiled language (see below). I’m afraid it’s ironic enough that I’m going to have to leave it!
February 18, 2009 at 10:26 pm (Note to Self, Oracle)
To find all sessions for a specific user connected via the Oracle JDBC driver:
select * from v$session where username='X' and program like '%JDBC%';
To kill all of these database sessions:
cursor c is
select 'alter system kill session '''
|| sid || ',' || serial# || ''' immediate'
and program like '%JDBC%';
fetch c into statement;
exit when c%notfound;
dbms_output.put_line('Executing: ' || statement);
execute immediate statement;
This will result in output similar to the following:
Executing: alter system kill session '225,46' immediate
Executing: alter system kill session '226,110' immediate
Executing: alter system kill session '233,6617' immediate
I’ve been examining HtmlUnit‘s performance from a couple of different angles lately. As a pure-Java headless browser intended for integration testing, one of HtmlUnit’s big draws is improved performance vis-a-vis native browsers and libraries which drive native browsers (Selenium, WebDriver, etc).
One the one hand, it’s easy to see that HtmlUnit reduces overhead by forgoing a GUI. No layouting, no drawing, no problem. If you poke around a little bit, you’ll also find that HtmlUnit does not download most images (there are some exceptions), nor does it download external CSS files if CSS has been disabled — all advantages in terms of network usage.
Not too bad, as it turns out (bigger numbers are better):
The good news is that Rhino is more performant than IE 6 or IE 7, so HtmlUnit still beats these browsers in this unrealistic worst-case scenario.