Few days ago I received a question about how to push data from the server code (C#) to the client side (ActionScript) though a messaging (publish/subscribe) destination. The server side is powered by WebORB for .NET and the client side is a Flex (or AIR) client. Read the rest of this entry »
In the following article I would like to show how to secure a Flex application which uses RPC (remote procedure calls) to communicate with the server-side. The article consists of three parts:
- A simple use-case and the problem description
- How to hack a Flex application
- How to secure it
The problem is not related to a particular product. However, the solution provided above is oriented only for WebORB for .NET. Well, let’s move forward to the step #1? Read the rest of this entry »
WebORB Management Console is a flex application to manage the installed instance of WebORB. There is a number of available features in the console, and describing them is out of the article scope. I would like to say that the unsecured and available through the internet WebORB console may be a gap in the system security. So, how you can secure the console? Easily! Read the rest of this entry »
The following article shows how to push data from the WebORB server to a connected client
Obviously, if you want to push data to a particular client you must identify the client somehow. Therefore, the first issue is a client identification and it might be done in two different ways. Read the rest of this entry »
In this article I would like to show how to use RTMP on iPhone, or on iOS in general. Although the RTMP protocol known as a part of Flash Applications, in this article you will not find the ActionScript code because the client library is completely native. At the end of this article you will find all important links and the source code.
Read the rest of this entry »
Few days ago Midnight Coders released a new version (188.8.131.52) of WebORB for .NET. Although the latest version contains a number of new features, I would like to demonstrate something that was not included in the WebORB release history – an ability to intercept audio or video stream data from the client on the server side for some additional processing.
To demonstrate the feature I created a sample application based on the simple use-case: client-side gets audio data from the microphone, encodes it with the SPEEX codec, and sends it to the WebORB RTMP server. On the server-side I intercept the received data, decode it, and save into a .wav file.
Read the rest of this entry »
To demonstrate this simple, but really helpful feature of WebORB for .NET let’s create a sample issue. An application has a simple service. Developers should be able to monitor all invocations from the client, and depending on the invoked method, the developer must create an entry in the log file. In this example, instead of a client’s application, I will use WebORB console. A server-side code is written in the Visual Studio 2010, and you will the find zipped project at the bottom of this article. Read the rest of this entry »
This article demonstrates an approach recommended by Mark Piller for solving an issue that was posted in Midnight Coders Developers Forum: http://www.themidnightcoders.com/forum/Default.aspx?g=posts&t=4050.
The developer that posted this issue wanted to implement a paging feature and make a filtered search on the client side. This is a sample I developed to solve this issue, that I hope helps others. All source codes you will find at the end of this article.
Environment. The server side includes .NET framework v2.0, WebORB for .NET (v.184.108.40.206), and MSSQL 2008 R2. The client side is a flex application. The sample project is written in Visual Studio 2010, and Flex Builder 4.
Overview. WebORB Data Management for Flex (WDMF) is one of WebORB’s features that provides an extremely powerful framework enabling developers to create data-driven Flex applications. Although this feature is documented well and developers can find a bunch of information in the Midnight Coder Developers Forum, the issue described in the post above had to do with handling large amounts of records, and filtering implementation on the server side. Read the rest of this entry »