Dan Kegel wrote: > On Tue, Apr 15, 2008 at 3:49 PM, AndyA <wineforum-user@xxxxxxxxxx> wrote: > > > The trouble really is the net stub. With that, since it is a CGI binary, > > it is called possibly as many as a thousand times for each loaded html page. > > I cant expect to load and dispose of wine each and every time the CGI binary is loaded. > > > > That may be so, but it has no bearing on whether you use wine or winelib. > > If you want efficiency, you should not be using CGI, which runs > a binary for each and every HTTP fetch. This would be a problem > even with native binaries, let alone winelib/wine binaries. > > I'm afraid I don't understand what you mean by the CGI binary > getting called a thousand times for each loaded page. That > seems excessive. How is your server architected? > - Dan Why does the intricate detail of how my server is architected matter to you? I've explained enough already, and you seem to have missed the obvious point. With that I have said already I'm sure your critique doesn't need my input. I'm trying to build with winelibs. If you tell me what *your* problem is, I might be able to help you with it. :) I'm not particulary concerned about efficiency, as it happens..... And I know that leads to perl or someone else's solution. Maybe I could buy your software? I suppose I could try out FastCGI, but where I'm at, at the moment, it wouldn't be a benefit to me, whereas compiling against wine would. I have a whole pile of prerequisites, that have already lead me to the choice that I have currently made. When there is a practical reason not to do it this way I'll stop, and go a different way. I appreciate that I am the worst programmer in the world, but TBH, it's not an unreasonable question. I'm not here to avoid a problem. I'm here to try and solve one. It's allright if you don't have the answers, you know.
