Ok, just wanted to point it out since the code in Bryans example would have stopped the callback from being triggered even if everything works correctly, so he should have used setAsyncMode there.
About the debate of the default values for async - could it not be an idea to have setCallbackHandler() also set asyncMode to true and have it false by default? Then it would rarely be necessary to call either setSyncMode() or setAsyncMode()? On Aug 14, 6:50 pm, Matthew Woodward <[email protected]> wrote: > Stefan wrote: > > Would it not be setAsyncMode() for callbacks? > > It seems though as as soon as you do a myProxy.setCallBackHandler() it > > sets asyncMode to true, even if you have done setSyncMode() before. If > > you call setSyncMode() after you done setCallbackHandler() it goes > > into syncronous mode and ignores the callback. But no, I can not get > > the callback to fire either. > > Right, I was saying to eliminate that function altogether since > currently it defaults to be in async mode. > > -- > Matthew Woodward > [email protected]http://www.mattwoodward.com/blog > > Please do not send me proprietary file formats such as Word, PowerPoint, > etc. as attachments.http://www.gnu.org/philosophy/no-word-attachments.html > > smime.p7s > 4KViewDownload --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
