Hi, I'm running something similar already on one of my web sites. I have to see if it is easy to do this automatic. Give a couple of days...
On 6/29/06, INeedADip <[EMAIL PROTECTED]> wrote: > > I think anyone using your library understands...because that means they > are also writing JavaScript...and are forced to deal with a bunch of > "things" because of different browsers. > Anyways, thanks for the library it works great.... > > So I've got this idea...tell me where my logic is wrong or why nobody > else has brought up anything similar. > > We have an administration portal here that we log into and monitor the > system. Now there are a number of different "proccesses" going on that > are created by our clients. Currently we monitor these from one page, > there are about 15 different "progress bars". I use your library to > get the status of each proccess and resize some images to mimic a > progress bar. > > This is one example of the different things I've got going on this > dashboard. There can be "MANY" Ajax calls queued up depending on what > web parts they have showing. > > So lets say I've got 30 tiny requests (AjaxMethods that return integers > or what not) queued up. Instead of having 30 individual calls to the > server (which is the most expensive part as far as time consuming) what > if there some kind of RequestBus (I don't know what to call it). > > So we do something like: > > AjaxPro.CreateBus(2000); <-- create a bus that contacts the server > every 2000 milliseconds. > > Then I could do something like: > > Ajaxpro.Bus.Add(new AjaxRequestOrSomethingWithACallback); > > So I could queue up a bunch of requests, and those get executed on the > server every two seconds (if there are any queued up), but all at once > (although I assume all the callbacks would get called sequentially > because of the two thread constraint). > > Does that make sense? This would be great in my dashboard example > because the data doesn't have to be "real time", I need to show the > updated data but not ASAP. While I understand that I couldn't have all > 30 callbacks being executed at the same time, it would still only make > one trip to the server. I hope I am explaining my self enough for you > to understand. This concept wouldn't be benefitial for any of our > other pages, but our dashboard and other pages that utilize web parts > would benefit. > > Any ideas, suggestions, or insults? > > > > > -- Best regards | Schöne Grüße Michael Microsoft MVP - Most Valuable Professional Microsoft MCAD - Certified Application Developer http://weblogs.asp.net/mschwarz/ http://www.schwarz-interactive.de/ mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info -~----------~----~----~----~------~----~------~--~---
