Sorry about not replying sooner, I was offline after I posted last
night.
Pops:
About passing parameters:
I tried to follow the example in the jQuery docs of using
jQuery.extend to handle optional parameters to functions - I think
it's like using named notation for parameters in PL/SQL - i.e. foo(bar
=> 5) would be foo({bar : 5}); in javascript. I agree that there isn't
really a standard though, and it wasn't quite clear from my comments
how it should work. Options is just a javascript object.
As for the single vs multithreaded issues, I understand what you said,
and I'm doing some googling to try to determine how setInterval is
handled (particularly because it is not part of any specific
standard).
Ganeshji,
I think that a periodic ajax updater would be a nice addition.
I'm thinking that the jQuery ajax object could be extended with an
additional parameter:
{ periodicFrequency : 10 }
This would then perform an ajax call every 10 seconds. There would
need to be a way to stop execution of the periodic call as well. Hmm,
something else to think on.
Thanks for the comments. I'll see what I can come up with.
On Aug 18, 7:38 am, Pops <[EMAIL PROTECTED]> wrote:
> On Aug 18, 5:59 am, "Ganeshji Marwaha" <[EMAIL PROTECTED]> wrote:
>
> > I am sure westamastaflash will reply to ur query, but in the meantime, since
> > i am still awake (3 PM here), i thought i will do a good deed before i goto
> > bed.
>
> > try $.periodic(callback, {frequency: 5});
>
> > You were using quotes for the options object. That was probably the cause of
> > the problem
>
> Yes, with alittle bit of swagging (scientific wild ass guessing) I
> finally figured it out. This is prime example of what I may call
> "obstrusive" about the different ways people use JSON for parameter
> passing. No consistent. Maybe thats good but it becomes a freaking
> guessing game. :-)
>
> --
> HLS
