Actually although everything looks hot, it is in fact not - we have a
recurrence of the "excessive path depth" syndrome in the mounted URLs
which will mean that the standalone version of Engage is almost
certainly broken again. Here is a standard link from the head of the
page below:
<link type="text/css" rel="stylesheet"
href="../../../../fluid-infusion/src/webapp/framework/fss/css/fss-layout.css"></link>
As you can see it has grown four up-segments where only two are
required. I've filed ENGAGE-216 and also want to draw attention to
Justin's ENGAGE-193.
I have committed a fix for ENGAGE-213 reworked slightly from Sveto's
original patch to supply content length as well as to guarantee stream
closing. We should now be able to use POST and PUT successfully from
within Kettle, and I have also added a "demonstration" patch to the
ENGAGE-213 issue which elaborates engageDemo.js to demonstrate this. In
this patch are also the beginnings of a rudimentary Couch "API" similar
to some of Joan's work in the scratchpad, including demonstration of how
to issue an HTTP HEAD request to retrieve a document revision number
from etags supplied by Couch. We should talk about these directions
further at the tech meeting on Thursday.
Colin Clark wrote:
Hey again,
Since I sent my last note, it noticed that Jacob has fixed the issue in
Engage trunk at r8878. I rebuilt the daily build, and it's looking hot
again:
http://build.fluidproject.org:8095/engage/artifacts/browse.html?db=mmi&q=Merchandising
Just a reminder to those of us committing code that breaking the build
makes everyone sad. :P
Colin
On 14-Dec-09, at 5:15 PM, Colin Clark wrote:
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
