It doesn't quite match XMLHTTPRequest, so I'd rather not rename it  until it's really the same.

On 7/22/06, Max Carlson < [EMAIL PROTECTED]> wrote:
lfc/kernel/LzHTTPLoad.lzs makes sense.  Shall we rename this to
XMLHTTPRequest since it now emulates that API?

-Max

Henry Minsky wrote:
>
> I have some common code between two kernel implementations of the same
> API, LzHTTPLoader.as and LzHTTPLoader.js . Where
> should I put the common code? It's code that is portable so that would
> put it someplace in the LFC, but it is used by kernel code.
> I am not sure how to structure this -- the LHTTPLoader.as and .js files
> define their own LzHTTPLoader objects and put methods
> on them.
>
> I'm thinking that this code could go into lfc/kernel, and be #included
> by the individual runtime files (lfc/kernel/swf/LzHTTPLoad.as, and
> lfc/kernel/dhtml/LzHTTPLoader.js)
>
>
> --
> Henry Minsky
> Software Architect
> [EMAIL PROTECTED] <mailto: [EMAIL PROTECTED]>
>



--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

Reply via email to