Ganesh schrieb:
Actually it was more along the lines of examples
of what we could reuse from dojo!
My understanding of transport is that it is hardly more that
instantiating an xmlhttprequest and queueing the callback. I'm afraid
"crossporting" the dojo code wouldn't do a great deal of change to the
code as it's pretty much the same in many AJAX implementations including
J4Fry and trinidad (please correct me of the parts if I'm overseeing here).
Yes I assume so, I personally just find the way the dojo people have
isolated the transport excellent with their xhrRequest objects
and callback functions cleanly isolated and easy to use. It is not an
order that we should integrated it :-)
But I checked out the transport layer a while ago, because I wanted to
reuse it, and that one was pretty hard to rip out! There are so many
dependencies into dojo that
it probably is harder to rip that out than to program your own transport
layer on top of xmlhttprequest :-)
The logging part in dojo in really good - but it depends on firebug!
Would you want to include firebug lite with MyFaces??? I'm not quite
sure of the size of it and it certainly needs lots of improvement and
bugfixing and the state we put into MyFaces would be frozen - we would
need to crossport new releases as they evolve.
You probably are right there, I was not too deep into the API again this
was just an example of a dojo part which might be useful for us :-)
A small logging api itself is a no brainer and can be done within a
short period of time (i did it in my code as well, with hooks into
console if present if not doing something else)
