python - The architecture of a real-time web chat app -


i create real-time web chat application using web.py in python. problem don't know how 'architect' or design such app.

the way i'm thinking implement app following:

  • a user logs app.
  • the app connects controller has push service push new messages , queue service store new messages.
  • when user sends message, app sends message ajax call controller , controller stores message in queue.
  • then controller sends messages in queue destination user push service.

however see poor design since see lot of ajax requests being sent here. don't know if there better designs or architectures such service. can please point me toward correct design real-time chat app?

alex,

this understandable question, thought when building own messaging application. way broke down app's functionality:

       user registration        user authentication        adding new friend username        approving friend        messaging friend in list (of course)        shows online , offline users        runs background service in order messages when application closed.        uses notification area when new message received.        quiting application(kills background service)

a few things realized after building application was:

  1. the back-end architecture simple mixture of simple crud application pub/sub functionality. can read more on pub/sub systems here. here's simple chat application built using ruby on rails. can @ reference, it's architected.
  2. you should think last steps listed in above functionality in beginning of app in end. if architect in beginning, final steps fall place! :-)
  3. if want learn concurrency , cool, suggest trying implement of frameworks discussed here.

please let me know if have questions!


Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more