Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Roopesh Shenoy on Aug 29, 2011
Microsoft Translator API exposes Translation services for developers using REST-based and SOAP based end-points. An open source project, Bing (Microsoft) Translator .NET, creates a wrapper around these APIs by using extension methods, making it much easier to build .NET applications that can use translation.
The Microsoft Translator API provides a lot of features such as -
When using these features in a .NET application though, they have to be called using HttpWebRequest object, which is not very intuitive and also quite verbose. What the Bing .NET Extensions library does, is provide extension methods to .NET objects, to make these calls much simpler.
For example to translate a text input in English to Arabic, instead of
string uri = http://api.microsofttranslator.com/v2/Http.svc/Translate?appId=+ appId + "&text=" + tobetranslated + "&from=" + fromLang + "&to=Arabic”;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(uri);
WebResponse response = request.GetResponse();
Stream strm = response.GetResponseStream();
StreamReader reader = new System.IO.StreamReader(strm);
translatedText = reader.ReadToEnd();
using the Translator .NET library, you can now just write
translatedtext = tobetranslated.BingTranslate(BingLanguage.English,BingLanguage.Arabic)
In fact, you can even use the language detection feature to avoid mentioning the source language -
translatedText = tobetranslated.BingTranslate(BingLanguage.Arabic);
There are other extension methods provided for the other Bing Translation API features listed above. A full description of how to use these features is mentioned in Mohammed’s blog post.
To learn more about Microsoft Translator APIs, you can refer the developer documentation.
Extension methods is a NET feature introduced in .NET Framework 3.0 that allows you to add methods to existing types, without creating a new derived type, recompiling or otherwise modifying the original type.
Automating Error Reporting for .NET Applications
Introducing SQLFire: a memory-optimized, high performance SQL database
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
The WebSphere Liberty Profile for Developers: An Introduction
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply