Wednesday, April 21, 2010

Moving up through the ranks

As I hope you all know, you can rank your cases in our Feedback system. You can tell us your top 5 most important cases and that affects the ranking the case has. We use this rank to help us determine what we should be working on.

Today I came across a bug that had been reported six separate times. The rankings of the cases varied from in the hundreds to the thousands. Needless to say, not a case that was likely to get any attention anytime soon. I went ahead and merged the six cases. Now the merged case has a ranking in the top 20.

This is an important reminder to make sure you search for cases before entering a new one because as the saying goes, "United we stand, divided we fall."

Thursday, April 15, 2010

REAL Studio Discounts for 1-Day Sale Tomorrow!

Need some relief after Tax Day? We've got you covered with a special 1-day sale, tomorrow only (12AM - 11:59 PM CDT)! All new REAL Studio and REAL Server licenses will be 30% off! Are you, or possibly a friend or colleague, interested in checking out REAL Studio? Buy tomorrow at the discounted price and you have 90-days to return it if you are not fully satisfied. A new REAL Studio license is a great way to enjoy your tax refund!

New licenses. 30% off. Tomorrow. Be there!

Friday, April 9, 2010

The new iPhone 4.0 SDK Developer License agreement

Many of you have heard by now that Apple has changed their license agreement for the iPhone 4.0 SDK. The change would appear to prohibit creating native iPhone applications with anything except Objective-C, C or C++. What Apple did NOT say is why they are making this change. There has been a lot of speculation but what we need is to know Apple's true motivation.

We at REAL Software remain interested in possibly supporting iPhone. I say "possibly" because we have never officially announced support for iPhone and I don't want this to be misconstrued as an announcement. We are contacting Apple to find out what the story is. Once we know that, we will let you know if our plans have changed.

Wednesday, April 7, 2010

The wonderful world of credit card processing

Every year, more and more credit card purchases are done online. In an effort to make transactions more secure, credit card companies are requiring higher levels of security for web servers that process credit card payments. PCI (Payment Card Industry) compliance requires that a server processing credit card payments use SSLv3. If you are not in compliance, your merchant bank may fine you and/or shut off your merchant account as one of our customers recently found out.

This may all be very interesting (or not so interesting) and you're probably wondering what this has to do with you. If you are writing applications that talk to servers via SSL, you might find those applications suddenly failing on you when the servers are upgraded to SSLv3. The default value of REAL Studio's SSLSocket.ConnectType property is documented as being 1, which would be SSLv2 or SSLv3. However, as it turns out, the actual default value is 0 which is for SSLv2 only. If you are using the SSLSocket, you should explicitly set the ConnectionType to 2 (which is for SSLv3 only). Better yet, use the built-in constant, "SSLSocket.SSLv3" to make your code more clear. We will be changing the default value to 2 for REAL Studio 2010 r2 but you should make sure your code is explicit so you don't have to worry about this.

If you are in charge of your web server and you process credit card charges with it, you should investigate PCI compliance before your credit card merchant company turns off your account at an inconvenient moment. You can check your web server for PCI compliance using this web site: