Hi Matt, > Well, it appears that my problem cannot be solved - you've added an >> error message now stating that I cannot do what I want, and >> unfortunately typeless_uri doesn't solve my problem as well.
> Nothing "cannot be solved" - it's just software, and it seems you've > uncovered a bug in uri_to_file that needs fixed anyway. What I meant with "cannot be solved" was that it appeared that you did not want to solve it. Of course (almost) anything can be done as long as we're talking about software. >> * Are the plugins included with AxKit2 meant as examples only to be >> modified by the end user, or are they intended as end-user code? If I >> modify a plugin, won't the modifications be overwritten by later >> updates? > It's a bit of both. I suggest if you're modifying then first copy > somewhere else and set PluginDir to the new path, or rename the plugin > - the names don't mean anything. I'm fully aware of that. However, following this advice would mean that next time you update some central parts of Ax2, me as well as my users would miss that update as we're using the non-default plugin. Of course I could just update my code as well - I probably will - but it still means developing in two branches for essentially the same functionality. Today I created a new module based on serve_file. Except for the usual red tape, it was a simple copy-paste of the original Ax code - and I then changed a single line of code. However, that single line gave an amazing perfomance boost to especially Firefox users: It appears that Firefox checks the validity of all pictures on every reload, and as the 'Not-Modified' system didn't work, it would reload every picture every time you returned to a recently visited page. Opera and Internet Explorer didn't seem to have the same problem. And the changed line? I tried setting the last modified header in my plugin, however, serve_file insisted on loading the mtime from the temp file and overwrite the value I supplied. The result beeing, of course, that browsers would reload the pictures all the time as the temp file would always have a new mtime. I also gave up asking you to change it as I expected an answer along the lines that 'AxKit performs so well that you don't need caching'. >> * I've now started writing my own modules that replace the default >> plugins. Unfortunately, I cannot find a way to let my plugins coexist >> with the default plugins. Is this a good thing? > I don't understand why not. Rename or set PluginDir to a new path. Hmm, > thinking about it there may be another bug there if you have two > different plugins called uri_to_file because the compiler doesn't add > the PluginDir to the generated name. That's a bug but an easy one to > fix. When I replace modules like uri_to_file and serve_file, I think I replace so central parts of AxKit that I may be starting a new development branch - and I don't want that to happen. However, the VDMS software I'm working at won't work without my modifications - and you cannot have two uri_to_file and two serve_file plugins working as default at the same time. > You're being a big help in finding the areas of weakness of AxKit2, but > you have to weigh that against the fact that you're not playing - > you're trying to build something real. Is that to be understood like AxKit2 is simply a playground to try new ideas? Whilst I respect that, it's definately not what I need right now... > Ultimately I think AxKit2 will be an easier deployment for your needs, > but maybe you didn't have any issues with mod_perl that way. I think the very hardest thing about AxKit1 was the lack of documentation. It wasn't until I got hold of Kip's book that I realized the full potential - and I had been using it for a long time then. I think the very hardest thing about AxKit2 is the lack of documentation... No, I love mod_perl and use it regularly to create the most weird apps you might imagine ;-) On the positive side: On Friday we had a meeting with the head of development at Ricoh in Japan - he's responsible for around 2,000 programmers - and he had never heard about AxKit before. Now he has - and he was quite interested. And I've brought my first Ax2 site online: http://www.skjaerlund.dk/sofus is my sons website, and it's created entirely using OpenOffice. It even performs well now - after my modifications ;-). Regards, Lars -- Lars Skjærlund Skovengen 111 2980 Kokkedal Denmark Tel.: +45 70 25 88 10 http://www.skjaerlund.dk/lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
