Webserver and other processes

I have a basic webserver operating but I am not sure how to "share the processor" so that other activities eg serial monitor port input processing and output or web client even can work together.

Even though the webserver has a "client.stop" at the end of its procedure, it does not seem to release the processor for any other tasks, except as it runs.

I put a timeAlarms Alarm.timerRepeat to print a notification to the serial monitor,but it only prints a pending time alarms print when the webserver processes a web request,

Its as though even with client.stop, the webserver is taking precedent over all other activities.

Another example I tried was to check for serial monitor input characters to cause a print to monitor , again any pending print is only sent as the webserver does (or finishes doing ) its own thing.

I would have thought whilst not actually processing a web request that after client.stop, the cpu should be free to do anything else required.

Any help/thoughts appreciated.

Any help/thoughts appreciated.

I think you should post your code.

Problem solved, well discovered.

I was using the Yaler service as web relay to access my remote Arduino.

Apparently the Yaler process (for Arduino) is blocking, it keeps their server open continually, thus precluding any other activities, except at the instant a client accesses the Arduino.

If one requires only the functionality of a remotely accessible webserver, then Yaler is great, and easy to use.

What I was doing works fine using regular Arduino ethernet operations, but this cannot give me remote Arduino web server access.

FYI I also discovered in my debugging that web browsers typically access a web server more than once , which caused me some confusion when I was counting the number of client access events.
The stripped-down Firefox browser "Light" only asks once.

FYI I also discovered in my debugging that web browsers typically access a web server more than once , which caused me some confusion when I was counting the number of client access events.

Not for the same file, though. You really need to pay attention to what the client is asking for.