|
| |
User Groups : Forums : SiteExperts : Microsoft .NET
:  |  Silverlight + LAMP question...
Ok, as some of you know, I occasionally do some work for a local high school sports site.
I want to do something similar to a "game tracker", with near-real-time updates of what's going on in the game (preferably without using a timer).
I was originally going to use Silverlight and sockets, but the site is hosted on a Linux system, so it's a LAMP stack. Although, I could use Silverlight for the front-end, I don't really know how to handle (or what to do about) the back-end of things. It would be database driven.
Ideally, I would want the system to work this way:
A play happens. Someone inserts the play into an interface (web-based), which the client detects, and then the client updates. The entire system would be web-based. For an idea of what I'm talking about refer to the MLB Gameday system, or NFL GameTrax (I think that's what it's called).
I know this sounds a LOT like sockets.
Does anyone have any ideas as to how I could do this? I'm thinking this may be something I could sell to other schools as well.
Anyway, I was thinking of using Silverlight and PHP somehow. The database on the backend is (obviously) MySQL.
Any ideas, or a point in the right direction would be GREATLY appreciated.Started By Monte on Nov 1, 2010 at 11:47:52 AM | | | 18 Response(s) | Reply |
| View All Replies | Goto Page: 3 2 1 | | | Terry Young on Nov 15, 2010 at 3:12:25 PM I agree with all the replies in this thread, ChrisRickard's included :D
Except for one thing, stress on server is not directly related to how you strike the balance on the timer interval. It does, but it's not a primary factor. The number of users is.
My two cents adds to the timer approach, and that is, I would only do the Ajax HTTP Request only if the previous one had already returned, and I would abort the request if there is no response in X-seconds then initiate a new request. Taking it even further, for X consecutive number of timeouts, then you might want to let the user know about it, or do something accordingly.
I once had a 5-second-or-so timer (eventually ended up being 10 or so, not the point), and while jQuery was out of the picture for me at that time, this is what helped me done the job instead: http://www.ajaxtoolbox.com/request/documentation.php
I particularly like that library for it's support for grouped ajax request, the ability to do something if a timeout occurs, and it internally aborts the request if that timeout occurs.
Life gets easier if you can already handle timeouts and abort requests if needed, and IMHO there's no perfect timer or interval until timeouts and aborts are handled.
| | View All Replies | Goto Page: 3 2 1 |
To respond to a discussion, you must first logon.
If you are not registered, please register yourself to become a member of the SiteExperts.community.
|
