Deon van der Merwe wrote:
For the WAP1 devices: true. But for the WAP2 devices you will need
something at the MMSC layer, correct?
depends...
Some WAP2 devices go always via WAP2 gateway (ok ok, let's call them HTTP
proxies), others do direct HTTP lookups.
But I guess having this as a
Hi Stipe,
On 5/26/06, Stipe Tolj [EMAIL PROTECTED] wrote:
Would you be open to a HTTP interface in mbuni that, if configured,
will make a HTTP (get/post) to a configured URL with the user-agent as
parameter.
This external service will then return a profile for the device. Maybe this
Correct on all counts. In addition, the mmsc should have the option
to ignore the wap-profile url and rely only on wurfl if one so wishes
it.
P.
On May 29, 2006, at 12:13, Deon van der Merwe wrote:
Hi Paul,
On 5/29/06, Paul Bagyenda [EMAIL PROTECTED] wrote:
Firstly I apologise for the
Hi All,
Paul pointed me to the devel list with an idea that I have... The
discussion started after seeing that some Motorola phones (V3i) does
not include the x-wap-profile HTTP header. From the spec's it turned
out that this header is not madatory (to my great surprise!).
I am playing with a
