Jump to content

Recommended Posts

Posted (edited)

True it may not, has not been tested under pressure. It all depends on how the Java RMI Library code for the server processes requests such as blocking/non-blocking. Currently I'm assuming, not always good, that it is non-blocking and therefore a new thread is begun to service each new request. The other limitation is the commandreporter.exe tool provided by Capita, it can be quite slow depending upon the detail of the report being run.

 

That said, I'm not convinced that all parents will all want to see if their offspring have safely arrived at school all at the same time. So the requests will be spread out over time which should allow access in a reasonable amount of time.

Edited by bantonia
Spelling correction
Posted (edited)
Just checked, the Java RMI system is non-blocking and does dispatch a new thread for each new RMI call. So as long as the service which processes the call is thread safe, multiple calls all should process correctly. So it's now just down to Windows and the commandreporter.exe. Each call will be serviced by a new cmd environment. I'm again assuming, dangerous, but again I'm hoping those who have coded these parts have done so in a thread safe manner, that there will be no cross talk and be non-blocking. Edited by bantonia
Added text

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...