Mobilidade é tudo

Boa tarde…

Alguém já ouviu falar da JSR 228? Ou, seu nome mais formal “JSR 228 - Information Module Profile - Next Gen (IMP-NG)”? Confesso que já tinha visto algo sobre a IMP mas nunca me interessei, mas quando li um resumo bem sucinto dizendo que a IMP é uma MIDP sem interface gráfica fiquei curioso.

Minha primeira leitura foi no JavaFree, e vi que a IMP é similar ao Mobile Information Device Profile (MIDP) versão 2.0, mas não provê as capacidades de display gráfico requeridas pelo MIDP 2.0. Posteriormente encontrei o texto “Deploying IMPlets based on Mimer SQL and Nokia 12 SDK “, que diz: Recently, a subset of MIDP has been approved, named IMP (Information Module Profile). The main difference between MIDP and IMP is that the MIDP specification includes human user interface features, while IMP doesn’t. IMP does not need a human user interface since its target environment is a standalone device, mainly communicating machine to machine (m2m). Neste link também encontrei o seguinte parágrafo: One device that implements IMP is the Nokia 12, which features a persistent storage of 1 MB and a RAM of 256 kb. Another one is the Siemens TC45 that features a persistent storage of 300 kb and a RAM of 128 kb.

Pra finalizar, encontrei um texto da própria Sun: The Information Module Profile (IMP) is a strict subset of the MIDP 1.0 specification. The primary difference is that IMP removes MIDP’s display and input mechanisms - in other words, the javax.microedition.lcdui package is gone. Instead, IMP devices must provide their own implementation-specific classes to handle any interaction with the user they need. For example, a device with a set of external lights may provide an API to turn individual lights on or off. User-interface classes are not required - if there’s no interaction with the user, there’s no need for any UI support. (Note, however, that if a device is capable of supporting the MIDP UI classes, the application must use MIDP rather than IMP.)

IMP supports all the other features of MIDP 1.0, including the Record Management System (RMS), HTTP connectivity, and timers. The MIDlet application model is also supported, although the IMP specification refers to compliant applications as IMlets (pronounced to rhyme with “gimlets”), for consistency with the profile name. An IMlet is really just a MIDlet, though: An IMlet’s main class extends javax.microedition.midlet.MIDlet. One or more IMlets are packaged together in an IMlet suite. The IMlet application descriptor and the manifest use property names starting with MIDlet-. An IMlet can be run unchanged on a MIDP device, providing the device supports the device-specific classes or optional packages the IMlet requires.

Pow, não sei vocês, mas eu aposto que a IMP vai possibilitar a criação de inúmeras soluções que antes não eram viáveis. Com a expansão dos PNDs (Personal Navigation Devices) e dos LBSs (GPS) o céu é o limite.

Att.
Ping