Monday, December 24, 2007

Apex and ADF, a Sad but True Tale on I/O and a Moment of Clarity for C Developers


A good two part series on APEX and/or ADF - demonstrating two similar yet different applications at the AMIS Technology Blog.

And some comments on the same at Patrick Wolf's blog.

Also at AMIS, news of the Oracle 11g Fusion Middleware technology preview.


I/O is often a bone of contention, with the storage team blaming the database and the database team pointing back a the SAN, here's a typical sad story from Doug's Oracle Blog.


Not C versus PL/SQL, really, but seeing the differences between the two. A couple of heads up at the Simple DBA Blog.

1 comment:

Dimitri Gielis said...


You might find it useful to read this article + comments too, about apex and adf:


Official, Youbetcha Legalese

This blog is provided for information purposes only and the contents hereof are subject to change without notice. This blog contains links to articles, sites, blogs, that are created by entities other than Oracle. These links may contain advice, information, and opinion that is incorrect or untested. This blog, links, and other materials contained or referenced in this blog are not warranted to be error-free, nor are they subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this blog, links and other materials contained or referenced in this blog, and no contractual obligations are formed either directly or indirectly by this blog, link or other materials. This blog may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. The opinions and recommendations contained in this blog(including links) do not represent the position of Oracle Corporation.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.