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.
On Nov 27, 2009, at 6:52 PM, Bill Bumgarner wrote: > My recommendation would be to continue with this architecture. Apache tends > to spawn a bunch of children -- either in the form of processes [old school] > or threads [new school -- IIRC] -- and you are quickly going to find yourself > in multi-threading hell if you try to integrate directly with Apache. By > running a separate server process, you can choose how and when you apply > multithreading hell to achieve scalability (if necessary). > > For your model, the key is to have the most efficient connection between > client [apache] and server [your image server daemon]. For that, rolling > your own may be the right answer. Then again, HTTP server <-> backend server > is a very well explored area of technology that may offer a pre-rolled > solution for you. > > 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
