Efficient storage/retrieval method for replayable comet style applications (Google Wave, Etherpad) -


I'm thinking of a web application with the same type of multi-user, automatic saving, infinite undo / redo Look at Wave and Etherpad (although on a small scale and on the userbase)

Before I went back and before recycling the wheel, something that is already a piece of technology or library, Or even just a design pattern.

I do not know that the best stack overflow question is because the "right" answer is not possible, but my Google-Fu has failed me and I just like a reading list!

Usually I will be developing under Python / Django but this firms are not just a preference :)

The club sandwich looks like a real technological:

  • The web page service and session management server code in the server and server

  • Server control conflict code

  • server control conflict resolution code in OLTP and comet INSTANT Messaging Server

  • In the client REM version control database Internals

  • Version control conflict in the client Resolution code (Inward bytes works in Balance Accountability from Clients - Client platform is single-threaded!)

  • Coment Instant Messaging Client Code operates in a batch on incoming bytes to increase accountability (client-platform is single-threaded)

  • Client GUI

  • (Optional) Custom bitmap font for a browser with poorly-understood font metrics

  • In customer GUI 2 D animation code (Runs in batch on the paint list to increase accountability - Client platform is single-threaded!)

  • Web user session management server code in client pages

Support continuous operation in the face of useless helper proxy servers The main design concern will be the flexibility of the network usage model Connection or bandwidth limit requirements You may be able to easily switch between comet signaling strategies and a different suite of time-bound borders, and to use The app to easily allow any limitations and problems in the field to reduce problems with the comet.

I hope the concern of the main implementation is achieving the lowest possible sequence of events between the GUI, by getting a change or confirmation in the condition of the carat (comet) and editing of text entry changes .


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -