DarkSocket - raw networking sockets, like MooSock

Ham · December 13, 2011 at 4:12 AM

Quote from SortaCore

Well, DarkSocket EXE supports all WinSock protocols, so if I make one for Flash, it'll support all Flash protocols
But with a lack of threads it'll be completely different to the EXE version.

That was promising! as long as the exe version is concerned, the posibility of a p2p conection was made possible the moment the activeX object was added to the list of MMF extensions. Certain behavioural problems makes it very difficult to reach and convince public in using an exe file which is to be installed. This problem was thought to be solved by vitalize. But the flash addon itself proves the degree of the existing disapointment from the vitalize. Flash has dominated a behaviour amoung public which is very hard to change and I think if you make one for the flash applications it will be very appritiated. I am reday to chip in and I am sure there are many others who are willing to have the same feature.

DJFuego · December 13, 2011 at 12:14 PM

Any further development with this extension re fixing the echo response?

Phi · December 13, 2011 at 8:20 PM

Quote from SortaCore

Currently I can't work on any of my extensions until the EDIF bug is fixed.
Please login to see this link.

Still applies, unfortunately the dude that has to fix it is busy with exporters and other things. It might take a while.
Having said that, the response-catching bug doesn't seem very obvious, so it might be a while after the EDIF fix.

DJFuego · April 8, 2012 at 10:38 PM

Has the EDIF issue still not been resolved? Come on CT, I could do with a really good network based object and this is stalling dark socket...

Stephen · April 9, 2012 at 12:09 AM

He could rewrite it in the rSDk if we aren't fast enough for you.

DJFuego · April 9, 2012 at 10:38 AM

Is the Bug really that insignificant that it doesn't warrant fixing to progress an extension that is going to allow MMF to make just about any sort of network based application? I realise that CT are working on other exporters and thats great but surely if SDKs are broken that's not great as it hinders the creativity process.

Phi · April 9, 2012 at 5:50 PM

C'mon DJ, they said they'll do it and they've only taken uh... about 5 months...
Yeah, a bit of speed might be cool around now...

Phi · April 19, 2012 at 8:50 AM

This is why I did a pre-release, having a bug for this long would just really honk people off if I claimed it was a full release version

wii1mii · April 11, 2017 at 5:01 PM

What did i do wrong ?
Please login to see this attachment.

Phi · April 11, 2017 at 6:12 PM

As with all Windows extensions, if you can see it in Fusion editor but not build it to runtime, copy the MFX from Extensions to Data\Runtime.

In this case, copy DarkSocket.mfx from Fusion\Extensions folder to Fusion\Data\Runtime folder.

advaith · April 11, 2017 at 11:01 PM

Quote from wii1mii

What did i do wrong ?
Please login to see this attachment.

Also, make sure the extension supports the exporter you're using.

Phi · June 4, 2022 at 11:48 PM

DarkSocket was updated to build 4. It's now out of pre-alpha "crashy" stage, and now in alpha!

Changes since build 3:

Now uses DarkEdif SDK v13 and its goodies: errors have the Fusion event line in them, Windows XP+ compatibility, extension version update checking, Fusion 2.0 and 2.5 compatibility, etc. Probably can be ported to Android/iOS later!
Int64 is now accessible by text expressions, replacing the "long" actions.
"long" was actually pointless in DarkSocket build 3; it was basically just another int32, same as integer, as "long" in 32-bit apps is 32-bit wide, and int is 32-bit wide in both 64 and 32-bit apps.
Linking to file output was removed. Keeping that feature spiralled the extension into manipulating binary before it sent it to the file - which, while very useful, isn't in the scope of a socket extension, more of a binary file extension.
Ideally, the Binary object will be ported to other platforms - if I get the source, and put it into DarkEdif, it's definitely possible!
Going independent and turning off logging was removed. That was just poor design choice.
Anything referencing memory addresses now uses text expressions. This is so 64-bit platforms can still communicate their addresses.
Text setting/getting now uses explicit text encoding parameter.
It supports UTF-8, UTF-16, ANSI and other explicit codepages like ISO-8859-1.
On non-Windows, though, there is no OS conversion feature readily accessible, so it's UTF-8 only. Still, most protocols use UTF-8 nowadays.
Adding to the ~~formed packet~~ built packet can now be done with both insertion and appending, depending on the index you pass.
Sending to the server socket's clients no longer uses a text parameter for client IDs.
The idea was that the Fusion dev would pass a list of socket IDs "0, 5, 8" etc, but this was never implemented.
As a future feature, I could set up an internal listing inside DarkSocket so you can group clients together. But I'll save that for if I see demand.
Removed the popup messages and test actions.
I had test actions in pre-alpha just to make sure the content was being set properly. I kept them public for later debugging.
Added a pending data cache.
Received data is now appended to an internal cache, so the Fusion events can find the end of message, as messages can be broken over several packets. This means you don't have to read or copy out everything for each packet.

I also updated/fixed the DarkSocket example included with the extension. There's also a help file!

Folks who want it before public release can subscribe to the Please login to see this link.. $15+ tier gets you extensions before public release!
(or contact me with your story of woe and haggle for a lower price, if you must)

Phi · July 7, 2022 at 8:50 PM

DarkSocket was updated to Please login to see this link., and publicly released!

Changes since build 4:

Now has smart object properties. If future versions change object properties, the Fusion developer won't need to re-create the object in the frame.

Phi · July 26, 2022 at 2:35 PM

DarkSocket was updated to Please login to see this link..

Changes since build 5:

Fixed corrupt minified JSON file, which caused built EXEs to fail to load at startup with a JSON error popup.

Phi · October 11, 2024 at 9:07 PM

DarkSocket was updated to Please login to see this link..

Changes since build 6:

Fixed misinterpretation of address in Build packet > Set binary action
Fixed crash when client sending when client is not connected
Updated to DarkEdif SDK v19

Log in or register!

Looking for Customer Support?

DarkSocket - raw networking sockets, like MooSock

Participate now!

Useful Links, Resources & Information

Fusion 2.5 Resources

Crowdfunding Focus