hi,
we are using the ajax scheduler in an mvc project. Looking great, good functionality, all that.
But we are encountering a serious problem.
The scheduler requires web service binding to work in an mvc page. Appointments are fed by the web service. Collecting appointments takes some time delving through the database.
All goes well until the web-service receives a request from another user requesting for appointments while it is still working on collecting appointments for the first user. The result is that the second user will receive both the appointments for the first user and her own appointments. Which is in a multi user scenario with high demands on privacy of course absolutely inappropriate.
This scenario takes some effort to reproduce. We found the proof by adding one "debug" appointment in the GetAppointments implementation of the service. The appointment was labeled with the requesting users identification. I case of heavy load an appointment mix containing two different "debug" appoints show up in the web page. Ruling out any bugs in our appointment collecting.
At the moment I'm studying on a workaround where the OnPopulating scheduler script event will make an ajaxcall to the service to raise a Mutex. The mutex will be lowered in get appointments. Quite a freaky way to solve things, provided it will even work. For now I don't see an alternative yet.
Any help is greatly appreciated.
kind regards
Peter
we are using the ajax scheduler in an mvc project. Looking great, good functionality, all that.
But we are encountering a serious problem.
The scheduler requires web service binding to work in an mvc page. Appointments are fed by the web service. Collecting appointments takes some time delving through the database.
All goes well until the web-service receives a request from another user requesting for appointments while it is still working on collecting appointments for the first user. The result is that the second user will receive both the appointments for the first user and her own appointments. Which is in a multi user scenario with high demands on privacy of course absolutely inappropriate.
This scenario takes some effort to reproduce. We found the proof by adding one "debug" appointment in the GetAppointments implementation of the service. The appointment was labeled with the requesting users identification. I case of heavy load an appointment mix containing two different "debug" appoints show up in the web page. Ruling out any bugs in our appointment collecting.
At the moment I'm studying on a workaround where the OnPopulating scheduler script event will make an ajaxcall to the service to raise a Mutex. The mutex will be lowered in get appointments. Quite a freaky way to solve things, provided it will even work. For now I don't see an alternative yet.
Any help is greatly appreciated.
kind regards
Peter