OK thanks - will do. One issue has arisen which deserves discussion (item 1 in my earlier post). The text replacement plugin can in some circumstances serialise a PNG image back to the browser. However, the existing code doesn't handle the HTTP headers correctly. The result is that the wrong content length is sent and browsers sometimes don't display the image.
My proposed solution is to avoid this simply by removing the ability of the plugin to stream its images. Instead it simply writes the PNG image to the cache, which is within the web dir. By one means or another, the browser is given the <img> tag with the src URL pointing directly to the cached image. This approach has some advantages: * it fixes the bug by simply removing the offending code * the resulting code is simpler and therefore easier to test and maintain going forward * it means that Apache/IIS is doing the serving of the image and this should benefit overall performance compared to serving from the PHP app. However, the downside is that the plugin will lose the ability to cache images in a directory outside the web dir. My question is this: does this matter? I.e. will anyone strongly object to not having that feature any more? Rick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
