why aren't the servers written in Objective-C?

[thanx7]

Hi
I've been writing a client code for iPhone and a server side code on Mac.
I'm really new, so it's not that easy to finish up...
Well, I'm already done with the client side, and need to make the server side on Mac, but the problem is I can't find any of server code from google or any other web.
Especially, I want it written in Objective-C, but there's nothing...........
So I really wonder if there's any problem if it's written in Objective-C.
Any comment would be appreciated
Thanks.

[akac]

You could...

cocoahttpserver - Project Hosting on Google Code

But its usually just easier/more secure to use Apache with PHP.

[naomipunkclan]

Hi,

You are best to go mainstream with the server side coding, e.g. PHP

The reason is you are out on a limb if you try and find a convenient host once you finish developing the Obj C code, you need to mess around getting a server with Obj C responding. Whereas say PHP - finding a host will be easy and you can shop around according to your needs and budget. Even if you wanted to serve from Amazon Cloud AWS you will find many mainstream AMI server images that cater to popular server platforms are already for you to use. So it may be a false economy to stick to Obj C even if it is your favourite language.

I can think of the convenience you imagine to get from using the same language and data structures on client and server. But in reality, it is not like that in web development. Usually Javascript on a web page, but server side javascript is not at all popular

Using CGI gateway, you can in theory run any language you like on the server, but mostly it is extra work, and probably not as optimal in runtime either. The first web App I developed was in standard C because that was all I knew at the time, and cgi gateways were the only way to go then. Now most server technologies are optimised and installed as a plug-in to the server. All the online help and the products and services you might leverage are catering to popular mainstream choices. So I would advise to research first the popular options and find a choice that meets your needs. On the other hand it depends on how big the project is - if you are doing all the work yourself and can't farm it out, maybe the extra workload of configuring the server yourself is a trade-off you are prepared to make in order to save getting too deep with a new language.

All depends on your situation. If the weight of your development work is more on the iOS client end, and server requirements are light, you could make light work of picking up enough basic PHP to do the job. More important I reckon to design the protocols well so, if the thing gets too big, it is clearly enough specified to farm out some work.

It sounds like the server requirements are low, by your post; but maybe you have underestimated...