indeed.. it's a pretty well solved problem.. so I'm using those as inspiration.. the documents we're editing are their own strictly structured format in my app.. hense not just going ahead and using google docs.etherpad off the shelf ;)

my real question.. as I've not spotted it in the code out there yet, is whether I should be using 'one socket per editor instance', or using a shared socket and identifying the messages for individual editors using an id

i mean, if i were to say "no" was unnacceptable, i'd probably break the document into paragraphs, or some atomic section where entering and leaving the section caused a merge, with conflicts queued up and pausing all merging until resolved (saving still to the server, but not as the golden copy)

sri: With $c->param() no longer returning a list, there doesn’t seem to be a reliable way of getting a list of all parameters any more, and going through $c->req doesn’t seem to include params defined in the route