Re: [Devel] user-agent and x-wap-profile integration
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 independant layer for both, wapbox and mbuni
available would be a good approach.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
___
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org
Re: [Devel] user-agent and x-wap-profile integration
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 external can make use of the WURFL database to create a response for mbuni to use (when no wap-profile is provided). Aaaa, ok, you want a wurfl to wap-profile converter. Ok, that way we could use the wurfl database and issue wap-profile back. Would be a good idea. At least if the overleaping of the details are common, otherwise we had to much lacking information. Actually this may be layered in the WAP/HTTP proxy, rather then the MMSC layer? For the WAP1 devices: true. But for the WAP2 devices you will need something at the MMSC layer, correct? ___ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
Re: [Devel] user-agent and x-wap-profile integration
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 mailing list being down -- disk space issues! I think WURFL integration as a fallback is a good idea. It should also be fairly easy to implement, as all that's needed is a parser that converts the WURFL format to the internal UAProf structure used by Mbuni. Something to add onto the todo list. The internal memory lookup for the UAProf structure: - it can be done on the x-wap-profile header - if the above is not found, it also uses the user-agent header Is this correct? For the second case then: the actual URL of the x-wap-profile does not matter. Correct? ___ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org ___ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
