The only problem I have with the image idea is that it is not particularly generic and a bit unusual (i.e. kindof a hack).
The IFRAME would need only contain a simple JavaScript function call, so it would be pretty small (the data would probably be less than the HTTP header information), and this would basically represent the framework for implementing RPCs via JavaScript. Once you go down this path, you don't have to worry about figuring out what image size means what or how to generate these images, you just pass a meaningful parameter to your RPC response handler. But, I admit, I can get religious about these kind of things. In the end, sometimes practical realities justify hacks. And, really, it is all a matter of degrees (I am not sure IFRAMES were designed for what I am proposing you use them for either). Jeremy --- Marco Tabini <[EMAIL PROTECTED]> wrote: > The image should take care of the click, and also > reduce the amount of > information transmitted somewhat (although not > necessarily, depending on > what you send to your iframe). > > Cheers, > > > Marco > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php