I'm writing my own awake handler for this, I just don't know how should to deal with his situation :)
hmm, not sure what is the problem...you should be able to handle that situation using the READ/WROTE events, no?
So should there be some loop in READ event?
something like until some-mysterious-condition [copy port/data] ?
I think first you need to know how much you read already, how much is left to read, if you are at the end of the response or not etc. and build logic around that in the awake handler. What protocol are you trying implement?
Also look at the examples...I don't remeber it from my head directly but you can either read or write on the port from the READ event depending if you want to wait for more data or send something to the server etc. It all depends on the protocol definiton.
Rebolek, IIRC you just call READ again on the port if you want to read more in the 'read event. That will trigger a new 'read event once new data is ready. You should check existing examples (eg. HTTP), I don't know what the state of the documentation is.
this will trigger a new 'read event where you call COPY again etc.
This is from memory so I might be wrong.
For example, in the HTTP scheme, in the 'read event I call the check-response function, which determines if more data is needed (do we have all the headers? do we need content data? etc.) and calls READ on the port accordingly.