On Nov 27, 2009, at 4:30 PM, Mr. Gecko wrote: > Well I'm wanting to be able to write image generators and other things that > is near impossible to do in php or any other web scripting language, also > running compiled source is faster then a script. My idea is to write a module > so I can just use a SDK that I will write to make different things in > Objective-C. For now I have a custom server in cocoa that when you visit it, > it returns a image based on parameters and this module would really make my > life easier.
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
