That's simply not how HTTP user agents work. You send IMG tags, LINK tags, etc. with *references* to URIs of other resources (images, style sheets, etc.), and the *client* then initiates further requests to get them (or not, depending on caching, user preferences, etc.).

Thanks - I was curious as to why it seemed that a FILTOSTR [html] "response" seemingly passed style sheet tags, but not image tags.

At anyrate, it did work out for the better. In addition to presenting the html, some "client" values needed to be set (you helped me with that {js ONLOAD)-thanks}. It would have been difficult (well, it would have required two responses anyway) to set "parent" frame variables and asset (F2STR html file). What I ended up doing was to include a "requesting" url (for the html file) after the local variables had been set by the init.

So instead of two responses for one request, a second request for the html (path and name stashed in a server file) was returned to the browser. It seems to hit fairly quick as local host. I reviewed the source JSP solution - and it seems that it is also delivering two responses, though one (the control state response) [i'm guessing] is an active server page service.