Interesting stuff to think about. Since all
web output must consist of streamed bytes
and all streams must have some backing
store, it is necessary to have an <img> tag
to have an endpoint for the stream.
It is easy to create dynamic images which
are simply output to the stream, but these examples
I have sent you provide a way to direct
the stream's output to a particular device
context (the <img> tag). This is really no
different than the WinForms model of being
able to associate a Bitmap image with a control.
I think that the HttpHandler will
work fine to accomplish what I need.
After reading some articles on the web
it seems that it is necessary to keep
the handler separate from the control
which uses it, so the easiest way to
use the handler is to just place it in the
root folder of the app. I found an article
which demonstrates the use an Asynchronous
handler an I will use that to implement
my controls.