没有合适的资源?快使用搜索试试~ 我知道了~
首页The_Dalvik_Virtual_Machine
The_Dalvik_Virtual_Machine
需积分: 9 11 下载量 4 浏览量
更新于2023-03-03
评论
收藏 151KB PDF 举报
Java has always been marketed as “write once, run anywhere.” The capability has largely been made possible by the Java Platform, the foundation of which is the Java Virtual Machine (JVM). Although this goal has largely been met for the Java platform on desktop (JSE) and server (JEE) environments, the mobile Java ecosystem (JME) is a bit more fragmented with various configurations, profiles, and packages causing significant modifications to applications in order to support different devices.
资源详情
资源评论
资源推荐
David Ehringer
March, 2010
THE DALVIK VIRTUAL MACHINE ARCHITECTURE
Introduction
Java has always been marketed as “write once, run anywhere.” The capability has largely been
made possible by the Java Platform, the foundation of which is the Java Virtual Machine (JVM).
Although this goal has largely been met for the Java platform on desktop (JSE) and server (JEE)
environments, the mobile Java ecosystem (JME) is a bit more fragmented with various
configurations, profiles, and packages causing significant modifications to applications in order to
support different devices.
While Google has selected Java as the language for developing Android applications, it has
chosen to abandon both JME and the JVM in favor of an alternative deployment target, the Dalvik
virtual machine. Google has also chosen to use an alternative and limited implementation of the
standard Java libraries. Both of these are non-standard Java, and effectively represent forking of the
Java platform. This seems to break from the trend of people targeting the JVM as a the runtime
platform for a very wide range of languages. Scala, Groovy, JRuby, Jython, and Clojure are only a few
of the dozens of languages that run on the JVM. These languages can not only take advantage of
the many features of the JVM but also seamlessly leverage all the standard Java libraries and the
countless custom libraries created by individuals and organizations. Recently, Google has been
subtlety bucking this trend by created non-standard Java technologies. This includes non only the
Android platform but also Google Web Toolkit (GWT) and Google App Engine, the reasons of
which they are non-standard is beyond the scope of this paper as they aren’t mobile technologies.
But the trend may be applicable to what has happened in the JME space. Non-standard Java
implementations may further fragment the platform cause additional headaches for developers
looking to support the wide array devices currently on the market.
This paper looks to understand the architecture of Dalvik virtual machine and understand the
technical reasons for why Google chose to developer their own non-standard virtual machine.
While there are most likely also business reasons behind creating Dalvik, this paper only addresses
technical considerations.
Design Constraints Imposed by the Target Platforms
The Android platform was created for devices with constrained processing power, memory, and
storage. The minimum device requirements for an Android device are the following:
1
Feature
Minimum Requirement
Chipset
ARM-based
Memory
128 MB RAM; 256 MB Flash External
myapi
- 粉丝: 0
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 收起
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
会员权益专享
最新资源
- RTL8188FU-Linux-v5.7.4.2-36687.20200602.tar(20765).gz
- c++校园超市商品信息管理系统课程设计说明书(含源代码) (2).pdf
- 建筑供配电系统相关课件.pptx
- 企业管理规章制度及管理模式.doc
- vb打开摄像头.doc
- 云计算-可信计算中认证协议改进方案.pdf
- [详细完整版]单片机编程4.ppt
- c语言常用算法.pdf
- c++经典程序代码大全.pdf
- 单片机数字时钟资料.doc
- 11项目管理前沿1.0.pptx
- 基于ssm的“魅力”繁峙宣传网站的设计与实现论文.doc
- 智慧交通综合解决方案.pptx
- 建筑防潮设计-PowerPointPresentati.pptx
- SPC统计过程控制程序.pptx
- SPC统计方法基础知识.pptx
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论0