MuSL stands for Mu Scenario Language, a canonical canonical Domain Specific Language that we use in Mu Studio to represent complex transactions between multiple hosts using multiple transports and layers. The language itself borrows constructs from numerous languages and was designed to be protocol friendly. We just published an interactive application protocol playground that shows off MuSL and how to use it for various types of testing including LTE, NoSQL, Databases, Layer2 and DPI.
Archive for August 2010
Scale Testing Outlook Web Access with Mu Studio
If you are building or deploying a WAN Acceleration or DPI product, chances are you will be dealing with Outlook Web Access (OWA) users from branch offices trying to get their mail working. You have to undoubtedly worry about scaling your products (and Exchange!) as your branch office gets larger with more and more people accessing this. As shown below, OWA is not just for the browser. You can have the Outlook client use the RESTful API over SSL without resorting or DCERPC firewall tunneling madness.
MuSL for Application Protocol Fuzzing and Scale Testing – Introduction
So we’ve had this thing called MuSL (Mu Scenario Language) for more than a year now in the Mu Studio product. It’s the format of choice at Mu for modeling everything from layer 2 through 7 across a wide range of applications, everything from LTE (Long Term Evolution), Databases, SCADA, Web applications, NoSQL to FCoE (Fiber Channel over Ethernet). Our customers use this for Functional Testing, Fuzzing and most recently Scale Testing. This is the first of a series of blogs describing what MuSL is and how you can use a single description of a multi-host, multi-protocol, multi-transport transaction for Application Fuzzing to Scale Testing.
