- Home
- Pattern Languages
- Liberating Voices (English)
- Liberating Voices (other languages)
- Liberating Voices (Arabic)
- Liberating Voices (Chinese)
- Liberating Voices (French)
- Liberating Voices (German)
- Liberating Voices (Greek)
- Liberating Voices (Hebrew)
- Liberating Voices (Italian)
- Liberating Voices (Korean)
- Liberating Voices (Portuguese)
- Liberating Voices (Russian)
- Liberating Voices (Serbian)
- Liberating Voices (Spanish)
- Liberating Voices (Swahili)
- LIBERATING VOICES (VIETNAMESE)
- Civic Ignorance / Anti-Patterns (English)
- Other
- Projects
- Community
- Digital Resources
- News
- About
- Contact
E-Liberate
Submitted by elemunjeli on Mon, 2013-02-04 00:29
I'm working to understand the examples of long-polling code I have so I can rewrite that aspect of the application. For concurrency streaming sockets are nowadays mostly preferred I think but our server won't support that. So I'm working with a restful architecture and a recursive method to count the statements already in the browser and then pass the arg back and forth. I'm not sure if this means the server needs to open a new connection everytime it completes a return, or if it can stay open for multiple returns, but I do know the query will stay open for a longer period if there are no returns which makes for much more efficient threading on Apache.
On Wednesday I worked with the Games team and will probably discuss more with them next week.
