Ferret.Net

[joewski]

Wow finally it works for me.
I just downloaded "simple chat".
All seems to work fine.
Went through the firewall ok. and everything.

Is there any basic doc's with this extension yet?

[Jeff]

No docs yet Joe <img src="/center/images/graemlins/smile.gif" alt="" />
That is one of the main reasons I have had such a hard time and been a bother to Turbo.

Overall the system is dead simple once you get over the hump.

I should begin to start my own documentation effort of the object as it might help me to make sure I understand what each action/command and event does.
Also to help out Turbo so he can continue to work on the extension without the time wasting documentation process <img src="/center/images/graemlins/smile.gif" alt="" />

[turboferret]

Thanks for the interest guys. I could upload a html doc with a simple description of each a/c/e with the next build, shouldn't take too much time <img src="/center/images/graemlins/smile.gif" alt="" />. I've also added Andos' suggestion to have actions/expressions for adding byte/short/long/binary parameters to send with functions.

Btw Jeff, it's no bother at all. Getting these questions and feedback is amazing for a project like this, where things are pretty complex and change fast <img src="/center/images/graemlins/smile.gif" alt="" />.

[turboferret]

[]
Turbo -- Can you check the data is coming thru correctly when a client disconnects?

I hate to be a pain in the rear but I don't think its working right

When I do
Client: On connection removed

and then add a line to the list box ClientConnectionName$( "Ferret.Net" )+" Disconnected"

It doesn't contain a name -- So I think the data isn't coming all the way thru.[/]
I think I've figured this one out now, I haven't looked at the source yet though.
The reason is probably that the connection is removed from the clients list at the instant the client receives the notification from the server. This will make the "ClientConnectionName" return the next name in the list, or "" if the removed connection was the last index. I'll fix this by removing the connection after "Client: Connection removed" has been triggered, instead of before.
I'll change the conditions to be a little more descriptive too.

[turboferret]

Here's the next build and I've got something new tucked in <img src="/center/images/graemlins/wink.gif" alt="" />

Blowfish encryption is now available. You enable encryption by choosing 'Blowfish' in the new encryption properties. Then you can choose to type in your own key, or generate a random one. At the moment the key is stored in plaintext, so I'll change this in the future to be more secure.

[James]

Awesome <img src="/center/images/graemlins/smile.gif" alt="" />

I still can't get server : on connect working though

[turboferret]

That's strange. It works here. What OS are you running?

[James]

Win2k professional, service pack 4.

[Jeff]

Jam just to be sure since I made this mistake.

When you do Server: On connect thats only going to trigger on the server not on each client. Server: On Connect is working in my super simple chat example (at least I believe so)

I kept trying to do server things on the clients -- once I quit trying to do that <img src="/center/images/graemlins/smile.gif" alt="" /> Ferret.net started to work a lot better for me.

[James]

Yeah, I am using it on the server - it doesn't work in your super simple chat example for me either <img src="/center/images/graemlins/frown.gif" alt="" />