|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 21
Messages: 21
Messages: 21
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
New Article: Working with J2ME
A cell phone application can be a good fit for certain types of problems, especially those requiring timely data access away from typical internet connectivity. Java 2 Micro Edition (J2ME) is one of the leading platforms for developing such solutions. This paper examines 2 approaches to connecting J2ME app to remote systems.
Read Working with J2ME.
|
|
|
Message #155252
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
some of this has been done already
More and more cellular phones will allow an application to retrieve the location of the phone. Such knowledge, combined with GIS data, can allow for unique and valuable applications. Imagine pushing traffic jam locations as a subscriber approached them. (Positing the existence of the back end systems, such a service is possible today, on some higher end phones.)
Back in 99, Neopoint demonstrated these kinds of features at CTIA. The sad thing is the carriers are purposely holding back location intelligent applications because they want to control it. Some of the carriers wanted to charge a tenth of a cent for each location call. If I remember correctly, when CDMA data speeds where 14.4, the max page size one could send was 1440bytes. More than that, it would get corrupted and fail. Since then it's gotten better, though I don't know what the practical page size is today. Another interesting thing with data calls is it takes 2 channels, instead of 1 like voice calls. Does anyone know of a main stream location enabled service today?
|
|
|
Message #155262
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
some of this has been done already
As far as I know, only Nextel gives programmatic access to this right now, and as you said, the other carriers are reluctant to making it accessible for privacy reasons (similar arguments apply to address books).
But I'm confident this will change, and that all it takes is one good application making a convincing use of LBS to persuade the carriers that the advantages will outweigh the risks.
--
Cedric
|
|
|
Message #155275
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
some of this has been done already
In Europe (at least in Russia) it is possible to get programmatic acccess to LBS. Just a yet another XML based interface. So we did applications based on that. Actually J2ME is not mandatory here.
Dmitry
http://www.servletsuite.com
|
|
|
Message #155299
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Strange ideas
As far as I know, only Nextel gives programmatic access to this right now, and as you said, the other carriers are reluctant to making it accessible for privacy reasons (similar arguments apply to address books).But I'm confident this will change, and that all it takes is one good application making a convincing use of LBS to persuade the carriers that the advantages will outweigh the risks.-- Cedric
Some V E R Y strange ideas thrown out in this thread. (The quote is only one.)
It is quite common in this day and age to propose any number of new services that may be fancy and even usefull without a thought about the ramifications of the proposals.
Even the fact that everyone are tracked rather well by the carriers is very problematic.
Giving this information out to others, even to an application runing on my phone makes it significantly more dangerous. Yes, even if the application have to run on my phone to get the localization information from the carrier. Any java game or other application could potentially get it and send it to someone else. I dislike such problems enough to want to stop even the possiblity via a law against it until we are sure the problems have been adequately addressed and that is determined by others than the carriers and definetely not developers of applications.
Here in Norway we reasantly heard in the news about one carrier offering a "buddy" service to it's subscribers.
Anyone could go to a page on the carriers web site, type in a phone number and an SMS was sent to that number saying: "xxx has requested buddy services from you. Do you want to accept this request?"
Without further explanations about what the service was.
If you answered yes to the request the one who had requested it could via the same web site track your location on a map.
Employers used it, wifes used it...
Nice service until you start to think a little about it's real usefullness.
Thinking helps.
Nils
|
|
|
Message #155311
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Privacy issues are major concerns
having worked on LBS, there are major privacy issues, which have to be worked out. The catch is, all the efforts that were started in 2001 for wireless privacy has faded away. Japan also has similar LBS. the US is still way behind Japan and EU on wireless. Back in 2000, there was a french company offering semi-realtime traffic data for Paris. It would simply show the major streets for paris. If a particular street was congested, it would be a thicker line. Not sure if it is still using 2bit images, but it was pretty effective.
|
|
|
Message #155326
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Strange ideas
Anyone could go to a page on the carriers web site, type in a phone number and an SMS was sent to that number saying: "xxx has requested buddy services from you. Do you want to accept this request?"
Without further explanations about what the service was.
In the information era, accepting a service request without knowing what it is.... well, anyone who does that deserves to be tracked.
OK, granted, there is a need to educate the public, but so what?
Thinking helps.
Especially when using technology...
|
|
|
Message #155334
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
It surprises me
I have talked with people about this before and most people don't seem to mind the idea of being tracked. This surprises me. They usually site some petty convience that could be gained by being tracked, and just assume that the technology would not be mis-used.
I wonder who would be the first to misuse it, the spammers, or the porn industry ;)
|
|
|
Message #155364
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
re: Source code
Unfortunately, the client code is owned by a company I'm involved with, so I can't hand out the source code. Sorry.
|
|
|
Message #155373
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
It surprises me
I have talked with people about this before and most people don't seem to mind the idea of being tracked. This surprises me. It shouldn't.
History has shown time and time again that people don't mind giving away their privacy if they feel they get something in return that's worth it. It's just a matter of finding the right price.
Location-Based Services are a very hot area and I know a lot of users who would definitely love to be able to ask their phone "find me the nearest mechanic that can fix a Toyota and show me the directions to it".
--
Cedric
|
|
|
Message #155375
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
It surprises me
I have talked with people about this before and most people don't seem to mind the idea of being tracked. This surprises me. It shouldn't.History has shown time and time again that people don't mind giving away their privacy if they feel they get something in return that's worth it. It's just a matter of finding the right price.Location-Based Services are a very hot area and I know a lot of users who would definitely love to be able to ask their phone "find me the nearest mechanic that can fix a Toyota and show me the directions to it".-- Cedric
Having built and used LBS, it is really handy. One of the things we did back in 99 was to take the long/lat from the phone, feed it to mapquest and do reverse geocode. Then we would perform searches based on the user's profile. Another neat feature which we built was tracking users. A cell phone user could give someone they know a password. That friend/family member could then go to the site, enter the password and see where the user was. At CTIA, we had an engineer from the embedded software division driving around San Jose, while the product manager gave a demo. At lunch, the product manager pull up the tracking page and saw the engineer was in a Mall. he called the engineer and asked, "how you doing." He responded "eating lunch right now." The audience got a pretty good kick out of it. Our team went as far as to drive around the eastern seaboard to test out the service and measure the quality of the triangulation. it's too bad the service providers wanted full control and wouldn't let other companies develop it.
|
|
|
Message #155477
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Network latency is a major issue
One issue you don't seem to mention is the big difference in performance between sockets and HTTP - on phones/carriers that do support sockets from J2ME you get pretty prompt network response, but through HTTP you are lucky to get sub-5-second round-trip times, which can be a big issue. Over GPRS here in the UK different handsets seem to vary between 4s and 8s to retrieve an HTTP response - so it pays to reduce the number of requests your app has to make.
Since the area I work in is networked games, where there are many roundtrips, it is a frustrating limitation.
|
|
|
Message #155482
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
I thought latency improved
Although I'm not surprised by this, I thought the industry had made significant improvements in this area. I don't know if this is still true or not, but with WAP, the WAP gateway is responsible for retrieving the content and passing it the phone. Because of how WAP provisioning works, each phone is assigned to a specific server (this may have changed). If a user is outside their main region, it means the WAP gateway handling the data is further away. With WAP, there was two types of browsers: micro and full. The micro-browser did not perform any rendering in the sense of analyzing the HTML/WML and then drawing it. With micro-browsers, the WAP gateway processed the markup and produced a binary page, which the browser just displays. With the full browser, the phone actually interprets and renders the page. I don't know populare micro-browsers are anymore, since phones have gotten much more advanced. In 99/2k, micro-browsers were used on smaller phones with limited memory.
now that phones are so advanced and come with much more memory, I'm going to guess most use full browsers. Are you using GPRS on the Orange network? I don't work on wireless anymore, but it is fascinating stuff :)
peter
|
|
|
Message #155526
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
re: Nahhh :) (sms)
I think that SMS is definitely a viable option that should be considered. However, a midlet has a couple of advantages over a SMS application. (This is based on my limited experience with SMS a few months ago, so things may have changed.)
Having an application on the phone means you can later extend that application, keeping the same user interface, and make it more valuable to the user. For example, in the paper, I discuss a trafic service. Perhaps the application could be upgraded to keep count of the number of times a particular crossroads was queried for, and the time. If this reaches a certain point, the application could pre-request this data every morning for your commute. Blue sky I know, but this kind of extension would be more difficult to do with an SMS based application.
Entering data is more difficult with SMS. Rather than clicks and selects (which are, believe me, tedious enough), you'd have alphanumeric entry. No chance for the application to help you out, either.
Can you send images via SMS? Even given the size of the typical phone screen, images can be a huge benefit and can convey quite a bit more information more quickly than text.
Perhaps you could have the midlet communicate over SMS, via JSR 120 and 205. I'm not sure how widely supported these are, but then you'd get the benefits of both.
|
|
|
Message #155566
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
major downside of SMS
In the past I wrote a SNPP (simple network paging protocol) driver and the main limitation for SMS is delay. SMS gateways in the US do not gaurantee immediate delivery and often a SMS message may take several minutes up to 1 day. I know in Europe SMS is more reliable, but in the US, it is still rather slow. Another potential limitation is SMS gateways limit the number of messages you can send per second, so to get around that, you have to make a deal with the service provider.
|
|
|
Message #156335
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
XML parsing...
Which XML parser was used here?
Do you have any performance data on XML usage?
|
|
|
Message #156336
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
XML use cases
Since XML was brought up here, what are the use cases for XML on cell phones that Carriers are pushing for? One of them I know is for news streaming. Any others?
JSR-172 uses XML parsing.
|
|
|
Message #156795
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
XML use cases
I think the cases for using XML for communication are laid out pretty clearly in the article. The ease of debugging (you can use a web browser) and flexibility in changing communication content (including in future versions) were what really decided it for me.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
