[mtasc] XMLSockets, events, and -main
Allen, Christopher S.
CSALLEN at PARTNERS.ORG
Wed Sep 14 22:05:44 CEST 2005
It's certainly not the Server. Null bytes are being used to terminate the
packets. The MMC version wouldn't work wither if that were the case. It must be
something else, like the library that I'm using to abstract the XMPP bit. Will
look into it later and let you know.
Thanks for letting me know that there is nothing wrong with the onData event
using MTASC though.
From: mtasc-bounces at lists.motion-twin.com
[mailto:mtasc-bounces at lists.motion-twin.com] On Behalf Of Jos Yule
Sent: Tuesday, September 13, 2005 7:04 PM
To: MotionTwin ActionScript2 Compiler List
Subject: Re: [mtasc] XMLSockets, events, and -main
Andy Dwelly wrote:
> I see from reading through the list that there might have been a problem
> getting event handlers to work if -main was used (around April). I've
> just started experimenting with MTASC, and I'm trying to reach back to
> the webserver where my web pages and swf file came from using the
> following code:
I've been doing quite a bit of XMLSocket programming with MTASC and have
not had these problems. I use a Python server that i've written myself.
It sounds like your server might not be ending each line with the NULL
(x00) character? This is required for flash to trigger the onData call.
mailto:jos at theorganization.net
MTASC : no more coffee break while compiling
More information about the mtasc