Anyone built or heard of an iPhone client to Wonderland ? It would be a great additional differentiator !
Another approach to consider might be having a JVM process on a server someplace serve as a proxy for a client with no Java support.
Yes, that is another choice.
My 2 cents:
In my opinion, in order to replace the WL client with some other client, it will be necessary to make a client -> server protocol that is fully defined and does not use serialized classes as protocol elements. Also, the protocol should be WL version independent. The way the protocol is currently implemented, most any change to a class that is moved across the interface would break a client that implemented the protocol.
With a client->server protocol that is 'data independent' it would be considerably easier to implement a new client.
/My 2 cents
You have a good bead on the situation, that is exactly what we had to do take this to the next level for mobility and other client stacks.
We defined an object system and implementation using Project DarkStar (that we call DarkNebula) that would do what was being done with Java serialization, but using language neutral protocols. This made it possible to build a client that was Java(same client-side tech that we built for PW), Java in 2D, iPhone, as well as another browser based client stack.
Can you talk so more about it? Is there information somewhere about it?
I woke up this morning thinking about a client (or the functionality of a client) that would generate an audio/video stream (MP4?) instead of a screen render. I don't know how avatar control would work nor how screen interaction would work but it is an interesting thought.
The system was architected to support different wire protocols for different clients, we started with (custom) serialization because it was the simplest to implement.
One thing to bear in mind though is that WL makes extensive use of dynamic code delivery, so if you had to write a client with no java support it would only be able to offer a very limited experience. Of course if you have a constrained use case you could provide native implementations of the modules you cared about, but I'm not sure that would be the best use of the system or developer resources.
Specifically for the iPhone you would need to do 2 things, firstly compile all the java code to a native form (there are tools to do this), the second and the biggest challenge, is that you would have to change the module system for the iPhone client. The iPhone license (I'm not a lawyer, but this is my personal understanding) does not allow dynamic delivery of code to the phone, so you would to precompile and deliver all modules as part of the client.
IMI demoed a prototype of a virtual world technology on iPhone that functions similar to Wonderland last Fall. We are aggressively moving to a private beta at the beginning of Q2 2010 and will be looking for folks to sign up to help us define the user experience.
Any member of the Wonderland community that is interested can send an email to firstname.lastname@example.org and we'll get you set up as soon as we're ready to go.
We can't wait to share this system with the community!
Message was edited by: dclingman
Other than the April fools day joke that Bernard posted (http://blogs.sun.com/wonderland/entry/fooling_around_in_project_wonderland), I haven't seen anything.
I thought the web browser client had a lot of potential for bridging the gap into the mobile space though (http://blogs.sun.com/wonderland/entry/a_web_browser_for_wonderland)
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.