blog for developers
One of nice features of Nokia E51 is it has Wi-Fi modem embedded. That gives you a lot of opportunities. I was particularly interested in Skyping my friends from my mobile.
First I checked Skype homepage in order to find out if there’s a version compatible with E51. There’s not… but on Skype forum I read that installing version for Nokia N95 might do. Only then did I read the official description of Skype lite.
Continue reading ‘Skype for free on Nokia E51 mobile with Fring’
Recently I’ve come across some problems on managing trunk/branches/tags. As a result of manual merging two branches I’ve ended up with hours spent on editing conflicts and checking the system. It’s obvious this was not a good sign as new bugs might have been introduced.
I’ve decided to organise the way the revision control system is used. Below you can find descriptions of two most common scenarios.
One of my applications was supposed to use image having its URL. The Image was instantiated with the stream the server that stored the image file responded with after being requested as below:
// create a request for image HttpWebRequest request = (HttpWebRequest)WebRequest.Create(IMAGE_URL); request.Method = "GET"; request.ContentType = "multipart/form-data"; request.UserAgent = "Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0"; request.Proxy.Credentials = CredentialCache.DefaultCredentials; request.Credentials = CredentialCache.DefaultCredentials; // get response from the server HttpWebResponse response = (HttpWebResponse)request.GetResponse(); Stream resStream = response.GetResponseStream(); // create image from stream Image image = Image.FromStream(resStream);
It worked like a charm when TCP port was used (regular, non-decure connection) but whenever the image was available at a URL that was secured (https://xxx.xx) I was getting the following stack trace:
Software engineer at Intel Corporation.
Particularly interested in Microsoft .NET platform, Java/JEE and web technologies.
