not loving your job? visit the joel on software job board: great software jobs, great people.

updated: a researcher finds six easy steps to steal second life accounts with no need for users to lift a virtual finger.

i just found out about the "oracle innovation award" that you can get into if you are using jdeveloper/adf and have an application that integrates with either oracle e-business suite, siebel or peoplesoft application. you can win free passes to oow sf and more. nominate your company and get more info here.

just published on the oracle ace program homepage: find oracle aces and ace directors on this google map. cool! view larger map share this ---related articles at eddie awad's blog:now i knownew oracle ace definitionwhat’s so special about the world cup?a thank you and a couple of picturesworld population = world population + 1

the oracle apex team has just published a white paper about integrating oracle application express with paypal payments pro. they have also created a which you can use to immediately start of.

good work jason! there have been several postings on the otn forum where people where looking for such an instruction to integrate paypal into there application.

security, and online crime, is a global business, but services can help companies deal with it better than standalone products, says matt medeiros, ceo of sonicwall, in this it link podcast.

edison集团比较了sun solaris容器技术与ibm逻辑分区及hp虚拟分区技术，说明solaris容器相对ibm和hp的类似技术的优势。 下载此报告

[[ this is a content summary only. visit my website for full links, other content, and more! ]]

this post is continuation of my series of post about database resident connection pooling.
let start with session and processes. my test shows that pooled servers are shown in v$session view only when there is user connected, that means session is busy. for inactive servers only process in v$process view is reported. to identify this processes we can run query like that:
select * from v$process
where program like '%(l0%)'; if our connection pooling is started, at least one process will be reported. this is so called connection broker that is authenticating connections and assigning them to another server for processing. according to my tests connection broker usually have highest number in brackets (ex. l003 if you set up max number of processes to 4). to see busy servers run this query:
select * from v$session
where program like '%(l0%)'; note that connection broker is never reported in v$session view.

in next test i've tested if global variables in packages are stored between connections. my test confirms that packages are always initialized after new connection is taken from pool. that's very good, and is what i was expecting. this is advantage over traditional connection pooling at client side like in java, where environment is totally shared between consecutive use of the same connection.

my next test was concerning usage of context. i've created sample context, initialized it in session and reconnected. i've ensured that session was assigned to the same process (pooled session) and read context. my test also confirmed that context is reinitialized between connections. in traditional connection pooling it will not happen. also when using php and persistent connection you have to take care of clearing global variables and context after acquiring session from pool (or before giving it back to pool). database resident connection pooling will make programmers life easier, at least on that field.

my last test for today was performance test. test was run on rather poor desktop machine with single processor.
(责任编辑：admin)