Server extension

I took a day off today and decided to write a server extension for Lacewing -

http://jamie.aquadasoft.com/LacewingServer.mfx

Untested and no docs/examples, at least until tomorrow or something. Enjoy! :)

Also (as it will get buried by this post) I wrote an article about stack messages tonight, if you've been wondering how to use them.

Jamie, where do we put this .mfx? In both Runtime and Extensions?

Thanks

Marv

Just Extensions will do if you only want to use it via "Run application", but you can stick it in the Runtime folder if you want to build EXEs.

yay!

Thanks Jamie,
is this as fast as pylacewing?

Faster, due to being multithreaded C++. Obviously things start getting slower when you add custom behaviour as events (MMF2 is single threaded).

Lacewing server implementations aren't exactly CPU intensive, though. Use whichever implementation you're comfortable with - speed should be the least of your worries.

Could you maybe make a lua plugin for it?

:D

Or maybe Retriever can.

I think we both would like to see a Lua binding to the extensions and/or lacewing directly. But it's a matter of having time to work on one.

I've been testing this out, haven't had any problems so far. We'll see how it goes, but imagine if there were no bugs for the first release!

Thanks Jamie for the info on the mfa placement.

Marv

Wow, from looking at the menus this seems pretty good so far! I haven't tested it yet, but I have a few questions:
A. would it be possible to assign a different channel master for a channel?
B. Would it be possible to change a channel's hidden state and destroy if channel host leaves state?
C. Can we force clients to leave channels, or join other channels? Also, I don't entirely understand something about channel names. Can we rename a channel that already exists?

Good work so far, Jamie!

Good work Jamie!

I always wanted this release but after Mathias told me about the Pylacewing implementation I don't think I could switch xD!

Good work jamie !

I'd like the server to be able to force a client to join/leave a channel though

you can do that Corentin. Just specify the user; Send a message to him; when received, disconnect

same thing for joining... specify user; send message to him; when received, join channel [name]

That is a less secure way to go about it. Clients could send messages to the server on that channel and hack it. Or they could block those messages.

At least that's what I've heard. Anyway it's something that should be avoided.

Client-side kicking is stupid. ;)
We'll have to wait until Jamie adds it - he'll most definitely do it.

Thanks for this extension ;)
I have a question : can we do a list of clients with your tool ?
'cause when i try to loop clients, it doesn't do anything :(

Are you sure you have clients in the first place? Are you using the correct loop action with the correct loop condition?

I have clients yes :P
I do :
Always :: Select channel by name"mario_rise"
Loop clients on channel

And then :
On channel clients loop :: InsertLine(Client_name)

I am having trouble with the server extension;
none of the conditions seem to work. for example, when a client connects to the server, the client connects, but the "on connect request" condition on the server never fires. even if I set the server to "on connect request -> Deny" the client still connects.

am I doing something wrong?

You need to enable the conditions first, using the "Enable condition" action.

but I thought that the "enable condition" actions were for allowing a request...

No, they're required for the condition to trigger at all.

and Jamie what it is done like that? Bandwidth saving, security?

It's for speed of course. The MMF2 runtme is much slower than the extension's internal runtime, apparently.

The server is multithreaded, MMF2 is single threaded. For a condition to be called:

* If the condition is enabled as interactive, meaning it can change the server behaviour, the thread in which the condition happens has to wait for the MMF2 thread to get round to processing extension events, trigger the event, and then resume the server thread again.

* If the condition is enabled as passive, meaning it can not change the server behaviour, the thread in which the condition happens pushes the event onto a queue, which is emptied by the MMF2 thread when the time comes around. This is much faster, but there's still a bit of overhead in the event system.

Still I don't get it as much as I want, but I see where are you going. BTW sorry for my previous post, I just noticed some grammar errors cause of my phone dictionary, rotfl xD

Quote:

---

Originally Posted by Fanotherpg

Still I don't get it as much as I want

---

What do you want? [crazy]

No nothing. Just I was a bit confuse by the whole talk, but it's OK now.

The server seems to crash when a player leaves (application closes). I had 1 player on the server (channel master) for 10 seconds, event triggered the player's game to close and the server crashed.

Edit: I think it's because the server tries to send a number message to a channel that no longer exists.

I know what the crash is caused by. It's fixed in the new build, I just want to add a few more things before I release it.

Ok. Great :) besides, it can be avoided by only sending data when there are clients connected.