[erlang-questions] Help my with Chat System

Summer nguyen summer0nguyen@REDACTED
Fri Nov 4 04:16:55 CET 2011

Dear experts,
Thank you for giving me suggestion.
After studying, I dedided the solution using Comet with mochiweb + ngnix  +
mnesia because of it's amazing performance  which is proved in the topic:


I will use the following design :
combet clients ---- nginx -----mochiweb --------- mnesia
---------mochiweb---------desktop clients

Wang Wei and Ngoc Bao suggest me to connect desktop client directly to
mochiweb instead of a Java backend Server
I don't use Ejabberd (or another exist Erlang Chat Server) because I don't
use most of the features of these Servers.(but I will use the source code
for reference)
And  I also have some specific logics in my Project. And it's a chance for
me to study a new  language.
Thank you very much indeed.

On Thu, Nov 3, 2011 at 3:20 PM, Samuel Rivas <samuel.rivas@REDACTED>wrote:

> >> I choose Comet because Not all Browser support webSocket ( especially
> old
> >> version browser).
> >> And number of users use old browser is so many.  am I wrong ?
> >
> > As for the old browsers - there are lot's of them but I would hate to
> > have to support programs
> > running on old browsers. If you want to support applications running
> > on old browsers
> > I think most problems will be in the incompatibility between browsers.
> Websockets are not even well supported among modern browsers. There
> are several versions of the protocol out there (it's still a draft)
> and some browsers pretty common out there have them disabled "for
> security reasons" by default.
> From the specification page in W3C (http://www.w3.org/TR/websockets/):
> "Implementors should be aware that this specification is not stable.
> Implementors who are not taking part in the discussions are likely to
> find the specification changing out from under them in incompatible
> ways."
> From the mozilla development site
> (https://developer.mozilla.org/en/WebSockets#AutoCompatibilityTable):
> "Warning: Among other things, a key reason WebSockets is currently
> disabled by default in Firefox 4 and 5 is the discovery of a security
> issue in the protocol's design. Using WebSockets in those versions of
> Firefox in a production environment is not recommended at this time.
> If you still wish to experiment with WebSockets, you may do so by
> opening about:config and setting the network.websocket.enabled
> preference to true. You will also need to set the
> network.websocket.override-security-block preference to true in order
> to allow initializing a WebSocket connection"
> Sadly enough it seems that the web community has been unable to
> provide a production-ready bidirectional protocol in more than two
> years of working drafts. As if it the problem were not serious enough
> just because a workaround like comet was already discovered ...
> That said, we have been using websokets in environments were we
> control both the browser and the server and they work fine (we were
> able to remove a lot of complexity caused by comet), but I don't think
> they are ready for public Internet applications.
> Regards
> --
> Samuel

Name: Nguyen Huu Ha
HCMC University of Technology
Faculty of  Computer Science & Engineering
Tel: 01699987252
Email: summer0nguyen@REDACTED
Y!h: summer.inthesun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111104/280ea9b1/attachment.htm>

More information about the erlang-questions mailing list