Hello,
I am considering designing a program, but as of now know little about ajax. I just want to know if what I am looking to do is feasible before I put a lot of effort into learning ajax. Basically, I want one file to make a request, but I don't want the request to be returned until another file is updated. How I see it working would be as follows:
1) User loads a page which gathers and displays initial data. A request for an update is sent to a processing file.
2) The processing file receives the request, but does not gather or return data
3) A third file, accessed by administration, is used to update information. When the updating form is submitted, a database is updated using the same processor file being used by the first file.
4) Once the database is updated, all pending requests from users are answered.
5) The user's file sends a new update request. This cycle continues until the user exits the page.
Like I said, I know little to nothing about ajax. I can program in HTML and PHP and perform queries on databases using PHP. I can get everything to do what I want it to except for updating. The only alternative I see is to have a page request information at regular intervals. However, this would cause lag in results and possibly unnecessarily update. So my questions are:
1) Is this feasible with ajax (or any other language)?
2) How much strain would it put on the server (assuming 5-25 users)
3) Where can I find more information?
Any amount of help will be greatly appreciated.
Thanks,
Clinton
Bookmarks