[vizionari]

hello.

are there are restrictions on which ports a midp application can communicate with, particularly on at&t wireless' network? i'm testing an application that communicates on port 8080. it works fine in the nokia 7210 emulator, but not when it's deployed to the phone. on the phone, the "G" and lock indicators appear, but there is no indication of a request coming in from the phone. any ideas what might be causing this?

also, is there a restriction that the midp application cannot communicate on a different port from which it was downloaded from? i downloaded my app on port 80, but conduct normal application data transfer on port 8080...

side question, what does the lock indicator mean when accessing the network? is data encrypted between the phone and attws's gateway?

last, is it possible to transfer data over SSL from a midp application? if so, is it simply a matter of getting an SSL certificate and connecting to "https://..." from a midp application?

thank you.

[rsmithh]

There are no port restrictions in MIDP. A likely explanation is that AT&T's WAP gateway is blocking the ports.

Although an even more likely explanation is you are falling foul of one of the many bugs in Nokia's http implementations.

[vizionari]

thanks for your reply. i will try to get in touch with at&t support about the ports.

re the nokia http bugs, is there a listing somewhere of what problems people have encountered? if not, can you briefly list or explain those problems?

thank you very much.

[roey]

is there an HTTPS support for J2ME through vendor APIs?

Thanks

[LiamQ]

Current Nokia phones don't support HTTPS from J2ME, unfortunately.