Tal, your HTML formatting was posted as part of the message, but it's mostly readable anyway. Here's the link to the old thread with decoding applied:
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2612147 I'm very interested to hear if progress has been made on this, too. --tim On Sat, Oct 1, 2011 at 5:30 PM, Tal Liron <[email protected]>wrote: > <html style="direction: ltr;"> > <head> > > <meta http-equiv="content-type" content="text/html; > charset=ISO-8859-1"><style>body > p { margin-bottom: 0cm; margin-top: 0pt; } </style> > </head> > <body style="direction: ltr;" > bidimailui-detected-decoding-type="latin-charset" bgcolor="#FFFFFF" > text="#000000"> > <p>Hi,</p> > <p>I would like to resurrect a very old thread, from more than a > year ago:</p> > <p><a class="moz-txt-link-freetext" href=" > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2612147 > "> > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2612147 > </a></p> > <p>Looking at the state of Restlet 2.1, I can't seem to find a > solution to the old problem, which implies asynchronous support is > still broken.</p> > <p>To rehash the problem:</p> > <p>Even if I set autoCommitting to false, parts of the Restlet > framework upstream will modify the Response (there is nothing to > stop them, since they have no idea about autoCommit downstream). > Their actions can easily interfere with my own "comitter" code, > which may be trying to modify the response at the same time. So, > the commit as a whole ends up being non-atomic and prone to race > conditions.</p> > <p>My suggestion back then was to throw a special exception class > that would force upstream Restlets to avoid any kind of messing > with the response. We don't like adding more exceptions, but in > this case there is an obvious advantage of using the exception > unrolling feature of the JVM to elegantly send messages upstream. > (Another solution would be to set a special flag in the response, > but this would require all upstream restlets to explicitly check > for this flag.)<br> > </p> > <p>So, I'm wondering what's the status of this now! This is a > feature I've been wanting to see in Restlet for years. The > potential is there (the concurrency stuff is well handled), but > there is still this missing piece of the mechanism.<br> > </p> > <p>-Tal<br> > </p> > </body> > </html> > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2848707 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2848708
