Hi Henry, Thanks for the update! So far, I've been updating the spec to reflect what I think the API should be, without worrying too much about how the current implementation looks. If you want to, feel free to do the same.
Also, perhaps we should consider renaming HTTPLoader to XMLHTTPLoader sine it can really only load XML. What do you think? -Max Henry Minsky wrote: > http://wiki.openlaszlo.org/KernelAPIProposal#HTTP_Loader > > > This is the currently implemented API. Probably needs another pass at > some point, there are > two places where LFC objects are being passed across the API that could > be done more neatly: > > 1) The constructor for LZHTTPLoader takes an LzDataset as an arg. This > is sort of a violation of > the kernel barrier abstraction. I didn't want to touch LzLoader on this > pass, but for the next pass over > this code I am planning to use callbacks and the LzXMLParser and > LzXMLTranslator APIs to > make this more modular across the LFC/kernel boundary. > > 2) The loadSuccess callback passes an LzDataElement back. It should > instead pass a string or native XML object > which is then passed to the LzXMLTranslator API, see above. > > > > -- > Henry Minsky > Software Architect > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
