June 5, 2007

Application Cache Refresh Call-back Trigger

Filed under: HTTPURITYPE, PL/SQL, trigger, UTL_HTTP, UTL_HTTP.set_transfer_timeout — Michael Moore @ 10:41 pm

This article has move to



  1. If I understand your code correctly, for each row update, you would have to wait for five seconds at worst or hundreds of milliseconds at best (time needed to get a page from an app server). It does not look like a good thing for performance.

    Comment by VJ — June 14, 2007 @ 12:34 pm

  2. Yeah, but what are the odd that all of the servers are going to be down? In my case, it’s very unlikely. Also, I would expect and average of 1 callback per minute, based on what I know about our system. But your point is well taken. Personally, the most I’d wait is 2 seconds: thinking that if I don’t get a response after 2 seconds, it’s not going to happen. If a person was really concerned about performance then this would not be a good solution. Probably they would want to use dbms_jobs. What would you do?

    Comment by Michael Moore — June 15, 2007 @ 4:57 pm

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Create a free website or blog at

%d bloggers like this: