WASP is, at heart, simply another example server for The Server Framework, but it’s also something a little new. Up until now potential clients have been able to look at the example servers source code and ask for pre-built executables for testing. The thing is, the examples are just that, examples and whilst release 6.2 of The Server Framework ships with over 70 examples (see here) they still only show small pieces of functionality in isolation. So, whilst it may be great for me to be able to test the number of concurrent connections that The Server Framework can maintain using a simple server example that doesn’t do anything much else it’s often not enough to convince people that they’re right to choose The Server Framework for their networking layer.
WASP allows potential clients, and non-commercial operations who don’t wish to license The Server Framework to build a server that does what they need it to do rather than what I want to show them. WASP will grow into a showcase for functionality that is available within The Server Framework. By writing your own DLLs you can plug your own business logic into our networking layer and to see just what The Server Framework can do for you.
But everything has to start somewhere. Right now WASP is fairly simple. It’s a Windows Service that exposes Performance Counters and which can be configured using an XML config file. You get to write a DLL which you configure WASP to load and once loaded your DLL is passed networking events as they happen. Right now this is purely an unmanaged TCP solution with no SSL but, going forward, I hope to add a host of features to WASP so that you can try out all of the key features of The Server Framework.
If your project is non-commercial then you can use WASP however you want to otherwise you need to buy a license to the pieces of The Server Framework that you need before you go live. WASP will give you the confidence that you need that The Server Framework can do all of your networking for you.