http://java.sun.com/products/javacomm/javadocs/API_users_guide.html I have used javacomm api (SimpleRead and SimpleWrite) from sun Java and I wrote a betterMessage 1 of 34 , Jul 6, 2002View Sourcehttp://java.sun.com/products/javacomm/javadocs/API_users_guide.html
I have used javacomm api (SimpleRead and SimpleWrite) from sun Java and
I wrote a better thread management.
you can use both windows and UX machines.
2 ways of programming
1-the easy in a infinite loop look for port input.
2-the hard the fast when a port input comes runs the event you run
I got COM Port hub for scalability.
I got write a management software for SMS Sending and Receiving.
almost %80 project cancelled.
Sorry, I have left that company 4 months ago and I have no source at
0212 287 02 32 (147)
From: moheb edwar [mailto:alashwes@...]
Sent: Sunday, April 06, 2003 1:56 PM
Subject: Re: [wmlprogramming] Re: How to communicate with gsm modem
I will be gald if u told me which class did u work with to communicate
with u r mobile
ibrahim CAKICI <> wrote:
I am a beginner but last year I have used a com port cable
to send messages from Java with ericsson GM32 GSM modem
--- In email@example.com, moheb edwar
> I was wondering how could i send at commands to Gsm modem or mobilehandset connected with a cpable from c# or any other programing
language r there any com i can use to send this commands to modem
Thanks a lotMoheb
>Please read the FAQ before you ask questions:
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> [Non-text portions of this message have been removed]
Visit http://groups.yahoo.com/group/wmlprogramming for archive and
Your use of Yahoo! Groups is subject to
Do you Yahoo!?
<http://us.rd.yahoo.com/finance/mailsig/*http://tax.yahoo.com> Center -
File online, calculators, forms, and more
[Non-text portions of this message have been removed]
Hello, Some comments about i-mode HTML are below. ... In general NTT DoCoMo is quite good at making sure their offered handsets meet the standards set forMessage 34 of 34 , May 6, 2003View SourceHello,
Some comments about i-mode HTML are below.
On Monday 05 May 2003 18:05, Boris Granveaud wrote:
> >For chtml, as far as I can remember (also checked some old messages) the
> > only thing that matters is if it supports emoji which should be supported
> > by default. Considering that we are going to put the markup group back
> > on, maybe we don't need this. Dunno. i-Mode guys, what do you think?
> emoji are supported by default on real i-Mode phones. However, the
> Motorola T720 for example is a WAP phone but it is also
> CHTML-compatible. The only i-Mode things it doesn't support are: emojis
> and UTN, the identifier the phone can send if asked in a link or in a
> form. Look for example at the UTN section in this article:
In general NTT DoCoMo is quite good at making sure their offered handsets meet
the standards set for i-mode. This means that the amount of information to
track about the handset can be considerably less than what is seen in the
WURFL. One thing that should be tracked though is that the i-mode European
emoji and Japanese emoji are not a one to one mapping. This means that if
emoji support is going to be defined, the WURFL should probably track which
emoji type a handset supports (None,European,Japanese).
I would like to reiterate that, as from the link that Boris provided, cHTML
and i-mode's HTML are not the same. I-mode HTML is an extension to cHTML so
things like UTN, emoji, marquees, and soon to be Flash tags are not found in
cHTML. Most likely many handsets claiming i-mode support that are not given
the i-mode brand will do cHTML and a possible smattering of i-mode HTML
Here is a list of the i-mode HTML tags and features.
http://www.nttdocomo.co.jp/english/p_s/imode/index.html [English link to
i-mode tags, not as up to-date as the Japanese link offered below. ]
Japanese links, but it is pretty easy to get an good overview of the tags
provided if you do not read Japanese.
http://www.nttdocomo.co.jp/p_s/imode/tag/index.html [direct link to the page
with i-mode HTML tag listings]
As the header does not require the version of i-mode HTML to be declared I
would recommend not having three types of chtml markup definitions in the
WURFL markup group. Perhaps two chtml and i-mode HTML (or just one). Then
we can set the supported i-mode HTML version tags in a manner similar to the
Nokia Series bases in the WURFL.