Wrox Programmer Forums
ASP.NET 2.0 Professional If you are an experienced ASP.NET programmer, this is the forum for your 2.0 questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old March 15th, 2007, 10:35 AM
Authorized User
Join Date: Jan 2006
Posts: 91
Thanks: 0
Thanked 0 Times in 0 Posts
Default Possible Conflicting Callbacks

I'm using this form of callback (aspx page-side code)


        function CallBackClientSender(varDataString) {
            //alert("at callback sender")
            var Command = varDataString;
            var context = new Object();
            context.CommandName = "CallBackClientSender";

        function CallBackClientReceiver(varCallBackResult, varContext) {
          //alert("at callback receiver")
          if (varContext.CommandName == "CallBackClientSender" ) {
            //alert("calling client-side router")

        function onError(message, context) { // This will occur if there's an exception from the server side
          CallBackErrorProcessing(message) } // message will be the exception message


 I've got two things going on that use the above mechanism to communicate with the client.

 One is a "prompter" in the page-side javascript that does this (next bit of code) repeatedly, basically "pinging" the server for app status info every so often

setTimeout("CallBackClientSender('" + wrkDataString + "')",gvPromptInterval )

The other is a set of buttons/transactions that do callbacks instead of postbacks.

 Once in awhile one of the button/transactions will "fail to operate"....the associated highlighting works, so the button isn't dead, but the callback clearly doesn't happen.

I suspect that a "prompter" callback may be happening right then, and the button/transaction call back gets "lost".

I'm looking for a way to keep these two sets of callbacks from getting tangled up with each other.

Any suggestions on how to accomplish this, based on the above mechanism (not ready for AJAX), would be appreciated.


Similar Threads
Thread Thread Starter Forum Replies Last Post
Conflicting Libraries in VBA References echovue Access VBA 1 July 11th, 2006 10:56 AM
2 questions about asynchronous callbacks pooh2006 ASP.NET 2.0 Professional 0 March 24th, 2006 11:20 AM
Conflicting Event Handlers chp Excel VBA 3 February 24th, 2006 03:00 PM
Conflicting References.... john_hearn Access VBA 0 April 21st, 2004 07:08 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.