It would also be really great if it supported all the other Java specs,
like Java 3D, Swing, AWT, RMI...
And .Net applications. And native Windows x86 applications (including 64
bit executables). And MacOS applications (including the old "System x"
ones built for the PowerPC architecture, nah, make that Motorola 68K).
And if it had support for X11 with hardware accelerated 3D.
Oh, and don't forget being able to run iPhone applications, natively, at
twice the speed of the latest iPhone.
All working seamlessly in a unified workspace.
That would be the ultimate mobile device operating system.
</irony>
Seriously, EJBs is probably not a good choice for a mobile application,
Android or not.
You can look at delivering a web/intranet application, or use JSON /
XML, or, if you're feeling adventurous, SOAP, to break up your
application into tiers. Those are good choices for a mobile application,
are available on Android, and will probably make your application a
better one in the end.
-- Kostya
04.02.2011 10:05, koala пишет:
> What about for tablet users?
>
> would that be such a nightmare too?
>
> So, If we have to develop an enterprise application are android
> devices so unable to deliver such?
>
> would it not be handy if android supported all Java SE functionality?
> including rmi, swing, etc?
>
> The fact that it supports it does not mean everyone has to use it.
>
>
>
>
>
>
>
> On Jan 21, 1:41 am, Jake Basile<jakerbas...@gmail.com> wrote:
>> It would be very convenient for developers, and a nightmare for phone users.
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment