Lacewing Build #17

Both extensions

* Lots of bugs fixed

* Lacewing can now be global across sub-applications

* You can now have multiple instances of Lacewing in one application (by setting the "global identifier" in the object properties)

* New stack cursor feature lets you read through a stack without maintaining a separate index variable

* You can now loop with loop names, so you can have multiple loops easily

* Message sizes are now unsigned shorts as per the protocol spec, so you can send longer messages

* Updated to the new protocol version (the same as pylacewing 0.8). This makes servers/clients using build 17 incompatible with previous builds.

Client only

* All updates above affect the Flash version too

* The "loop finished" conditions were not called in Flash

* Fixed a bug with channel/peer selection and loops

* The client now responds to ping requests

* You can now retrieve the protocol implementation of the server (such as "DLL" or "Python")

* Crash when calling the "Push string..." actions in Flash

* Channel listing now works in Flash

Server only

* Each client in the server now has "local client data", which is basically a map of string keys to string values, to which you can assign data to store with each client

* Each channel in the server now has "local channel data", which is basically a map of string keys to string values, to which you can assign data to store with each channel

* You can now host a flash player policy server, to accept Flash clients

* The server now accepts HTML5 websocket connections (I'll be releasing the Javascript Lacewing implementation at some point, as shown at the CC 2010). Both the latest specification used by Firefox 4/Chrome 6 and the older specification used by Chrome 5 are supported.

* The server now sends ping requests, to prevent ghost clients/channels

* The client is now selected when an "On disconnect" condition fires

* New "Channel is hidden from the channel list" and "Channel is set to close automatically" conditions

* You can now retrieve the protocol implementation of a client (such as "DLL", "Flash" or "Python")

* Changing the requested name now works

---

There's also a new extension called Lacewing Webserver included. This allows you to host a HTTP/1.1 webserver controlled by MMF events (Please login to see this link.).

This build is numbered 17 because 15 and 16 were testing builds I sent to a few people. Please post any bugs you find in this thread

Download: Please login to see this link.

Ah, looks like I was using an old Client.as when I built the DAT file. Redownload - Version$ should read "Build #17B" in Flash now.

If you downloaded this build, please check it says build 17 in the extension properties. It seems I might have still had a ZIP of build 14 up there for a while!

It requires build 249.

MMF2 Developer 249 update: Please login to see this link.

Ah yeah, I forgot about that.. maybe in the next update!

Are you looking for client or server examples? The Lacewing protocol, sockets or the webserver? I'll make an example for you. Do you use any instant messenger?

I'm working on the documentation, but there's still a lot left to do

I've had that happen to me, too (and I've noticed the client crashes on close sometimes). It looks like the server isn't detecting the client disconnecting for some reason - I'll look into it.

There's a client example here: Please login to see this link.

I'll put a server one together when I get a minute.