>> Andy Lewis wrote:
>>
>>> what about I/O terms?
>>>
>>> sendPageBlocking
>>> sendPageNonBlocking
>>
>>
>> I still like the concept of "waiting" a lot more. In short, your
>> 'server' is waiting for you to come back. It would be like having your
>> personal thread allocated in the server, even if this is not the case.
>>
>> The best I could think of would be:
>>
>> sendPageAndHaveYourServerWaitForYouToComeBack
>> sendPageAndSetYourServerFreeToServeSomebodyElse
>>
>> :-D
>>
>> but of course I'm not proposing these method names :-)
>>
>> now, somebody with good english skills should srink those concepts
>> down
>> to a reasonable short sentence.
>>
>
> What do you think of these method names?
>
> sendPageAndBack()
> sendPageAndWait()
>
Well, as I've recently learned, it seems you're not really sending a page,
rather you are asking for the processing of a URI. As such I'd suggest
something more like:
resolveURIandWait()
resolveURIandContinue()
....
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
