If for some reason you want to contact me please send an IM or email to my google mail account.
I can also be reached on Skype as simon.palmer.
Or you can just leave a message somewhere on my blog.
If for some reason you want to contact me please send an IM or email to my google mail account.
I can also be reached on Skype as simon.palmer.
Or you can just leave a message somewhere on my blog.
RSS feed for comments on this post. TrackBack URI
hey there, Simon
I would like to introduce myself – my name (no, this is not a joke!) is Simon Palmer. I live in Johannesburg, South Africa. I am in IT as well.
Just an introductory mail.
Ciao for now.
Comment by Simon Palmer — March 27, 2009 @ 10:17 am
I am interested in getting the source code you were doing for the stackoverflow question about flex socket not working. Please refer to the link below.
http://stackoverflow.com/questions/1709467/why-does-the-flash-player-throw-a-sandbox-error-in-this-case/
To be honest, I have been having the same issue as your but with a different twist. The swf is loaded from the server but once in the client, the swf needs to open a socket in the localhost at a specified port to communicate with a local server communicating as a relay to a hardware installed in the client.
Anyway, I read all the post and have done most of the thinks placed in the comment even before I got to the forum. I was wondering if you could send me a copy of the source code.
Comment by Napoleon Tan — February 2, 2010 @ 8:43 am
Napoleon,
unfortunately I can’t send you the code because there are commercial constraints around it. Probably more importantly I never fixed the issue, so my code is in the same state as when I logged the issue at Adobe. James Ward got close and there’s every chance that it is not a bug at all and just an issue with the socket lifecycle in my code. However, I have parked that piece of development for the moment and am likely to re-design the entire solution to avoid it. It is very frustrating and has been a major stumbling block for my Flex/Flash work. The same code and socket strategy works fine with a Qt client using UDP rather than TCP, so there’s something weird going on.
If you find a solution I’d love to hear it – if you post it on SO as an answer you’ll get my up-vote!
regards
Simon
Comment by simonpalmer — February 2, 2010 @ 10:07 am