Jump to content

Talk:Client–queue–client

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Ringbang (talk | contribs) at 02:06, 2 December 2013 (tagged for Networking task force). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing: Networking Stub‑class
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by Networking task force.


This article describes the software architecture, and not a: person, group of people, band, club, company, or website.

Client-Queue-Client, also named Passive Queue, was one of the alternatives to classic Client-Server architecture, before Peer To Peer architecture was born, and it's still important to know, because it allows to create many software solution quicker, than using any other architecture, or design pattern.

That speedy-deletion "tag" was the closest one to fit the purpose. It now appears that deletion is not necessary. I did some copy editing and cleanup too make the article more readable. Realkyhick 19:35, 3 June 2007 (UTC)[reply]

Classic vs. Client-Queue-Client?

For readers not in the know, and I am among them, would someone describe the “classic” client-server model and how it contrasts with client-queue-client? Maybe illustrations such as those in the Peer-to-peer article? 75.5.198.8 (talk) 20:57, 13 January 2009 (UTC)[reply]