Ok, you don't HAVE to learn about OTP and behaviours, you can add these features after. It mostly has to do with fault tolerance. I would recommend chapter 11, which contains a server-client IRC example. You'd just transfer the client code to java, I think if you can master that, you'll be set. Although, I think the whole 'Group' aspect makes it kind of confusing.
You might also find some erlang TCP servers out there, I did some googling and found this http://20bits.com/articles/erlang-a-generalized-tcp-server/. There's probably more and better ones out there. You may also want to look into RabbitMQ if you can make it fit your needs. But the code in that blog is pretty solid and in my opinion simple and easy to understand. > My main problem with Nitrogen is trying to figure out how to interact > on the client side. I've installed the firebug extension into firefox > so I can view all the requests needed to the server. There are > several Javascript requests and some requests are 100KB plus. It > seems like nitrogen adds a lot of overhead which is not something a > data plan could endure. I've found another Erlang chat example which > has far fewer requests than before. I've installed it on my server. > You can access it at http://stormyd.dyndns.biz:8000 . The code is > from > http://chrismoos.com/2009/09/28/building-an-erlang-chat-server-with-comet-part-1/ > . When using firebug, it shows two javascript pages and multiple GET > requests (the browser appears to cache the javascripts so it will only > be the first time). I understand how the client will long poll the > server for 1 minute 30 seconds until it responds, but I do not > understand all the setting up requests. Is it possible to emulate all > of the GET requests on android. Could I bypass the javascripts? If > you or someone could help me interact with the server through telnet > (logging in, posting messages, and receiving them), I think I'd better > understand how it works. > Wow, that seems like a lot of unnecessary overhead. Definitely stay away from that, my opinion is that HTTP should be used to transfer Hyper Text, or websites. Not game data. -- http://diastrofunk.com, http://developingthedream.blogspot.com/, http://www.youtube.com/user/revoltingx, ~Isaiah 55:8-9 -- 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
