October 22nd, 2008 by Arjan Olsder Posted in Platforms: J2me | 1 Comment »
Unlike native Symbian games, J2me games have always been bothered with tight security restrictions on S60 devices, leading to endless popups, time and time again.
This problem has lead to a bad consumer experience in the past years when games needed frequent Internet access. The developers of the Java Runtime on S60 have now decided to change the policies.
With the new policies that will be active in Symbian 3rd Edition Feature Pack 3, users finally have the option to let the device remember their choice. With this option, the experience of playing connected J2me games will be much more satisfying.
Read the complete story here.
Congratulations
Your first AWS Elastic Beanstalk Node.js application is now running on your own dedicated environment in the AWS Cloud
This environment is launched with Elastic Beanstalk Node.js Platform
What’s Next?
- AWS Elastic Beanstalk overview
- AWS Elastic Beanstalk concepts
- Deploy an Express Application to AWS Elastic Beanstalk
- Deploy an Express Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Deploy a Geddy Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Customizing and Configuring a Node.js Container
- Working with Logs
That’s a nice update. I hated how my game had to ask for permission to use bluetooth every single time I ran the midlet. It wouldn’t be so much of an issue if getting the midlet certified wasn’t such an ordeal (or as expensive!)