Any interest? I'll probably be doing my own version of Razor's crypt.dll.

Features:
gets raw packets from server or sends raw packets to client
C++
fast
IPC is via memory mapped files (one for output from client, one for input to client)
thread signaling is via semaphores (real signaling, not for (;;) loops hammering the CPU checking for work to be done)
thread safety via mutexes
I'll probably add in EUO style macros later (circletrans,pathfind,etc.) as I have all that code written from a previous project

IPC code is written and tested.

I won't be adding in client decryption because I already have all the code for that in managed code, and my options will be exposed to managed code, so it makes sense to keep that side of the process patching over there.

The only downside is this is the first C++ code I've ever written, so it might look a little strange...but it will be organized.

Very interested. Have thought a lot about this myself over the years.

I do agree that it should be a streamlined .dll. I don't think there's any need to do anything in C++ that could otherwise be done on the managed side. I.e., keep it maintainable

VC++?

Keep us posted!

Will you be doing this in C++.Net or "normal" C++?

Sounds interesting either way.

I was really pleased with the development of UO:98 that was done in C++.Net, and the migration of Batlin's UO Demo DLL code from Borland to Visual C++ was virtually painless. The benefit of doing it in C++.Net is the ease of talking to it from managed code ()

=D

!

I'm just going to stop talking about it until I make up my mind =D
I keep redesigning the thing, but I'll end up with something decent. At least it's a proper self-injecting DLL now with an empty DllMain.

Things will be slow for a little bit as I'm in the middle of reorganizing my businesses.

Thanks for the update. I'd love to have time to be more involved. Soon though I hope.

please see:
viewtopic.php?f=28&t=1152