The image is different for each and every person and I can't cache it. The disk will already be used to get the php to run which generates the page the image is on. I know this may sound like a Captcha, but it's not. I will continue to try and write this module and if it works out, then I'll be happy. I'm already working on my first step, getting mod_example to compile in xcode.
On Nov 27, 2009, at 7:55 PM, Bill Bumgarner wrote: > > On Nov 27, 2009, at 5:08 PM, Mr. Gecko wrote: > >> My idea was to basically write a module that runs NSTask to start the cocoa >> binary and just have a framework to like manage the server information and >> talk to the module, by printf I guess, saying like which headers to return >> and the data so I can set the content-type to image/png if I wanted to >> return a png. Well all I can say is it's really complicated, I guess all I >> need is to write a module that runs exec(); and handles outputs until it >> quits. > > As soon as you get NSTask into the mix, you are likely going to kill > performance [and might as well just use straight CGI, at that point].... > > If scalability matters at all, you are going to want the image creation to be > handled by something that sticks around long enough to cache and otherwise > avoid the cost of repeated startup and disk I/O. > > If there is any text parsing or other transformation between whatever your > server or process spews and what is sent back to the client, you are likely > going to kill performance, too. > > b.bum > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
