Out of curiosity, why is developing the client side for a nitrogen app so difficult? I'm a big erlang advocate, and I am happy that you've looked into it. If you really want to make a kick ass server erlang is a good choice. I would recommend you pick up Joes erlang book as it provies examples on how to make fault tolerant, scalable servers.
It's really not that hard, and a really good excercise. On the java side, you would just connect and communicate either via JSON or via bytes dirrectly. Working with bytes in java is easy using bytebuffer, and in erlang using the super awesome using the bit syntax. Plus you avoid the encoding/decoding overhead, and you can create a custom byte protocol that'll be as fast as it gets. Erlang provides ways to make generic servers easy using behaviours. You'll probably want to use tcp to guarantee packet delivery. If the connection is flaky. Either that or some sort of transaction system. Btw, I replied to your last post. I'm not sure if u got it. Hope this helps in some way. Miguel On May 30, 2010 11:50 AM, "ravishi" <[email protected]> wrote: Hello everyone, I am getting started in android development and I really want to create some form of online game. My goal is to start out with a turn- based game and move onto advanced multiplayer games. I want to have users associated with their google account, provide some sort of matchmaking to pair people together, have their stats stored in a database, and use the stats for various leaderboards and such. I have read over an older discussion on this list at http://www.mail-archive.com/[email protected]/msg75993.html . There was a lot of good information that I gathered but I still have some questions. What I originally started with is an apache web server on a laptop that I don't need right now (2.0Ghz Core 2, 3GB Ram). I wrote a perl module that can take in a user's name with a JSON GET request. However, I stopped this approach after learning that apache HTTPD is not very scalable for a large number of persistent connections. Therefore, I switched over to Erlang + Mochiweb with the intention of using Nitrogen. I used Nitrogen because I am looking for a comet based solution so I can avoid polling the server. There is a demo app that uses these three technologies that seemed perfect for what I wanted to do. http://nitrogenproject.com/demos/comet2. In that demo, it shows how users can post message and all client's connected will receive the message, so it is similar to how a game would work. After getting it set up, I realized that developing the client part on android would be very difficult when using Nitrogen so I'm about to give up on Nitrogen and possibly a bit inefficient as Nitrogen seems to be more about getting web browsers to do persistent connections. Erlang without Nitrogen might still be a path I could take. All I want is a server-client model that has persistent connections, comet based, and is scalable. But I need help in learning what technologies to use to get to this goal. Any starter code or links would be helpful too. Thanks, Ravi -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]<android-developers%[email protected]> For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
