Go Version 1 now on App Engine

Today, with the release of Go 1, a stable version of the Go language, libraries and tools, we're releasing a new Google App Engine SDK for the Go runtime.


Go is a statically typed, compiled language with a dynamic and lightweight feel. With Go you get the efficiency benefits of being close to the machine–your programs compile to native code–with the productivity and quick turnaround of a scripting language. Go apps are easy to write, start fast, and run fast. There has never been a better way to build scalable high-performance cloud applications.

The Go runtime provides clean, idiomatic Go APIs for the popular App Engine services (Blobstore, Datastore, Memcache, and so on) and a straightforward development process. As with the Python and Java SDKs, Go apps can be tested locally with the development server and, most convenient, the development server automatically compiles your Go code, so to test a change all you need to do is to refresh your browser.

The Go 1 SDK also brings improvements and bug fixes. It uses the new Go 1 time API throughout the SDK, provides a MultiError type for error handling in batch operations, and  supports Datastore Cursors and the XMPP and Log services. See the release notes for the details.

Although the Go App Engine runtime is still in experimental status for now, the language stability offered by Go 1 is a major milestone. To learn more about Go 1, see the announcement post at the Go blog and the wealth of documentation at golang.org.




- Posted by the Go and App Engine Teams

App Engine 1.6.4 Released

App Engine’s march of progress continues with another release that’s full of new features, system improvements, and bug fixes. As we spring forward into pre-Google I/O season, we’re keeping our focus on product polish and this release is a shining example.

System Wide Changes

• Logs - Now that the new settings for log storage have been available for one month, logs over the limit you specify will be deleted.

• Datastore Index Stats - The Datastore Statistics page in the Admin Console now displays the storage used by your Datastore Indexes in addition to your Datastore Entities.


• Blobstore Migration - The Datastore Migration tool now includes an experimental option which allows you to migrate your Blobstore objects during the migration process from M/S to HRD. We strongly encourage all applications to migrate to HRD.


• Datastore Backup to Google Cloud Storage - In 1.6.3, we launched backup and restore to Blobstore, and in this release we’ve added the ability to backup your data to Google Cloud Storage.


• Memcache viewer - We’ve introduced the ability to view Memcache statistics and examine memcache entries by key.


• Serve objects from Google Cloud Storage - You can now serve blobs directly from Google Cloud Storage as well as Blobstore.

Runtime Changes

• Threads - Both Java and Python now offer background threads when running on backends as an experimental feature. Additionally, we’ve added the ability to use threads for frontend requests in Java to match Python 2.7.

Datastore Framework Changes

• NDB for Python - The NDB API has graduated from experimental and is now a fully supported feature. This next-generation datastore API improves data modeling and querying and has been built from the ground up to support an asynchronous computing model.


• JPA 2 and JDO 3 for Java - We have made significant improvements to App Engine’s DataNucleus plugin. This experimental release of version 2.0 of the plugin adds support for JPA 2, JDO 3, and contains over 40 bug fixes. Check out the full release notes here.

And that’s not all, you can read about all the new features and bug fixes in our release notes (Python, Java). Send all your feedback to our Google Group, and if you have coding questions, find help from us and other talented developers on Stack Overflow.







- Posted by the App Engine Team

First-Party audience segments in the upgraded DFP service

Buying and selling ads based on audience has transformed the display industry in recent years. Buyers use new technologies to run highly relevant campaigns to users across ad networks and exchanges. This benefits publishers greatly, because it allows them to deliver more useful ads to their users ultimately helping increase RPMs on their indirectly sold inventory.



Publishers are increasingly taking control of their audience data as one of the key assets of their digital businesses. But publishers tell us they still want better tools to improve the integration, transparency, and control over their own audience data for both direct and indirect ad sales.



Today we’re announcing the first in a series of features in the upgraded DFP service that help publishers manage and control audience data through one platform, integrated directly with their primary ad serving technology.



This first release is focused on first-party segments - as a publisher, you will have the ability to define your own user audience based on criteria that you define (e.g., sports enthusiasts, travel readers). First party audience segmentation was available in the existing DFP service, and is now integrated seamlessly with the upgraded DFP service.



First-party segmentation involves no implementation or integration effort by you. Simply define the criteria you want for your audience segments, in DFP and DoubleClick technology does the work of populating them directly from the ad tag. Once you’ve defined your audience you can use it to increase the direct sales value of undersold inventory, and gain insights on how different audience segments are engaging with content across your site. We have designed it to be seamless, easy to use and to put you in control of your data.



First party segmentation is a great tool for our publishers, but it’s just the first step in the work of building out DFP’s audience capabilities. In the coming months you’ll see more information from us as we release a series of new features that are directly integrated with the upgraded DFP service.



Posted by Sean Harvey, Product Manager

Here is your chance to become a Bollywood Star!

T-Series launches a star hunt for the lead pair in Aashiqui 2 (sequel to the 90s super hit Aashiqui) on YouTube



It does not get bigger than this. If you’ve always dreamed of becoming a Bollywood star, here is your chance. Starting today - Vishesh Films and T-Series bring to you ‘Aashiqui 2 Star Hunt’ on YouTube. For the first time ever, the lead pair for a mainstream Bollywood film will be selected on YouTube. All you need to do is log on to: www.youtube.com/aashiqui2 and upload a 2 minute video from a list of scenes and songs on the Aashiqui 2 channel. Your audition videos will be screened by a Creative Jury, Producer/Director of the film and will subsequently go for Public Voting on the Aashiqui 2 channel.



When Vishesh Films & T-Series released Aashiqui, 22 years ago – it became one of the most successful musical blockbusters in Indian cinema. It gave movie goers and music lovers, music that people still love to listen to. Carrying forward the spirit of Aashiqui from Director Mahesh Bhatt & Producer Gulshan Kumar are Director Mohit Suri and Bhushan Kumar from T-Series.







You can also stay updated with all the news on Aashiqui 2 on the Official Google Plus Page of T-Series.

You can also join the Hangout on Google plus with Director Mahesh Bhatt on this page on Monday, 26th March, at 11:30 am.



This is a fantastic opportunity for aspiring and deserving artists to audition on YouTube and get a chance to be the Next Big Thing in Bollywood! Auditions Open Now!



Posted by Nikhil Rungta, Country Head Marketing Google India, recently watched Aashiqui Enact Scene 1

Doubling Down on Publishers

This morning, I had the pleasure of addressing the third-annual Admeld Partner Forum in New York. When we completed our acquisition of Admeld this past December, we said that we’d be looking at how to bring the best of their products and ours together to help us achieve our shared vision: helping our publisher partners make the web work for them, and get the most out of what online advertising has to offer. 



Over the past couple of months our teams have been hard at work figuring out exactly how this might happen. Today, we’d like to put our cards on the table and share what we’ve done and where we’re headed. 



Investing in the team: We realize that helping our partners succeed requires not just the right products, but the right people. So we’re investing in the team, bringing together our sales and services teams from across the DoubleClick Ad Exchange and Admeld. This enables a continued focus on high-touch service for Admeld’s publisher partners, and also boosts Admeld’s presence across the globe.<



Tapping new pools of demand: Next quarter, we’ll start offering AdX Connect, a way for Admeld clients to start getting access to demand from the DoubleClick Ad Exchange. We’ll also be enhancing the advertiser, buyer, and bid transparency levels in the exchange, so that they are comparable with those currently provided to Admeld publishers.



Connecting the dots with DFP: We’re taking two big steps towards tying together Admeld and DoubleClick for Publishers: making it much easier for publishers to leverage SSP-style ad network optimization functionality directly within the DFP platform, and building an API so that Admeld’s mobile optimization capabilities will be more fluidly integrated with DFP mobile.



While we’re excited about these changes, they are just the initial steps. Our long term goal is to create a single, seamless platform for publishers that allows them to manage all their inventory -- across desktop, video and mobile -- with the control and flexibility their businesses require. Our publisher partners make the web the wonderful place that it is today, and by empowering their continued growth and success, we all come away winners. 




Posted by Neal Mohan, Vice President, Display Advertising

App Engine Community Update

One of the best things about App Engine is our lively developer community. This week, we’re officially moving technical and development questions to Stack Overflow and retiring the language-specific App Engine Google groups. With this week’s move, we wanted to take a moment to highlight some of the best ways to engage with the community.

Technical & Development Questions
For technical and development questions big and small, add the google-app-engine tag to your App Engine questions on Stack Overflow. You can also join our hangouts or office hours to talk directly with App Engine team members.

Google+
Many community and team members are active on Google+, using the #appengine hashtag. Our weekly community updates and chats with App Engine community and team members are a great source of tips and tricks and to learn more about what our community members are up to.

Google Groups
For general discussion about the platform, use the Google App Engine group.

Happy coding!

- Posted by the App Engine Team

Google Voice for Android, now with Ice Cream Sandwich voicemail integration

(Cross posted on the Google Voice Blog)



Since we launched Google Voice back in 2009, we’ve supported visual voicemail so you could open the Google Voice app, see all your voicemails with text transcripts, and play them on-demand. But sometimes when I get a missed call, I don’t want to jump between my call log and the Google Voice app to see who has called me and what message they left.



So, today, we’re updating our mobile app so you can view and listen to your voicemails on demand directly from the call log on your Android phone. Your voicemails will appear alongside your outgoing, incoming, and missed calls in your phone’s call log and you can just simply touch them to play them. You can slow down the playback of the message which is great for when someone is telling you their callback number, or you even speed playback up, so you can quickly listen to longer messages.

To turn this feature on, download the latest app from Google Play and check “Voicemail display” under settings. This new feature requires Android 4.0+.

Posted by Yong-Hoon Choi, Software Engineer