与 Flash 通信的问题

我一直希望能用Flash做我程序的界面,主程序当然还是用VC写,这就需要网络通信.

查了半天help,发现了XMLSocket可以用，然后开个nc当server，用Flash连，发现可以连接，Flash也可以给nc发消息，但是nc发过来的就不行了。

帮助里关于onData隐约地说明了Flash接受到的消息一定要以一个\0结尾，我一开始就是这么想的，nc似乎发不了\0，于是我就弄了个简单的VC程序，不过一开始总不行，因为我用的是std::string("some words\0")，似乎std::string会自动切掉尾部\0,于是改为std::string("haha\0",5)，
啊，终于看到Flash有反应了。不错。

还有，Flash导出swf后，connect好像只会连接80端口，再转为exe就正常了，这有点好像调用外部exe的情况，估计也是为了安全吧。不过我用别的播放器，比如KMPlayer或Sothink SWF Decompiler就没这问题。

另外，据说Flash9的AS3已经没有这个问题了，我没试过，不知道是不是真的。

Comments

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later, gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with --userns=auto and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared various networking options and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

WangLu's Notes

Search This Blog