This content has been marked as final. Show 6 replies
I'm surprised no one has responded to this post, as it is a good question. I'd like to expand this question further to ask:
For what tasking is Oracle targetting this listener - development? packaged demos? single platform environments? laptops? Or is this a 'serious' production-ready listener that Oracle will push/recommend to be utilized in place of OHS going forward?
Very good question.
Does Apex Listener not generate more overhead than OHS/mod_plsql?
I'm interested in this as well. Is their a white paper on this etc?
I havenot seen any WP on this so far, I have been lookin for it too.
However it looks like the end of mod_plsql is nearing, if one tries to extrapolate from the trend. If you take a look at the Oracle EBS R12 stack the OHS+mod_plsql has been replaced by OHS+OAF+OC4J. In forms 11g Oracle AS has given way to WSL and forms listener.
In a nutshell , there appears to be a move away from the OHS mods_plsql stack in general. And apex listener is another step in that direction too.
So though in the short run OHS mod_plsql is the more mature middle tier , the future appears to be WLS/Glassfish/OC4J + listeners.
I start reading about Listener and this work over OC4J layer, also can use the AJP13 and AJP14 connector with apache (and use the compression_).
I am too new with apex, but for me is more natural work with apache + J2EE (Tomcat or other Java engine). That is a new alternative to work with APEX and maybe that is because some problems happen with OHS, so far I don't have so many time with OHS and APEX to give a better answer.