AG_DEVICEOS examples

Below are some simplified examples of mapping the AG_DEVICEOS URL macro to Web server directories and files. In these examples, the it is assumed that the Web server's domain is http://myserver.com, that this domain maps to the file system path D:\webserver\contentroot, and that you have two types of device OS to support: Windows Mobile Pocket PC 2003 and Palm. The value of AG_DEVICEOS for Windows Mobile Pocket PC 2003 is WINCE_OS, and that for Palm is PALM_OS.

  • Different files optimized for different device OSes, in same directory:

    Channel URL – http://myserver.com/myapp/AG_DEVICEOS.htm

    Files for different users –

    D:\webserver\contentroot\myapp\WINCE_OS.htm

    D:\webserver\contentroot\myapp\PALM_OS.htm

  • Different directories for different device OSes, with same file name:

    Channel URL – http://myserver.com/AG_DEVICEOS/myapp.htm

    Files for different users –

    D:\webserver\contentroot\WINCE_OS\myapp.htm

    D:\webserver\contentroot\PALM_OS\myapp.htm

  • Different directories for different device OSes, with different file names—as necessary for executables for your application.

    Use the different directories... with same file name approach, then within the two files, place links to the files that need to have different names on the two device OSes:

    Channel URL – http://myserver.com/AG_DEVICEOS/myappprograms.htm

    Files for different device OSes –

    D:\webserver\contentroot\WINCE_OS\myappprograms.htm

    D:\webserver\contentroot\PALM_OS\myappprograms.htm

    Content of ...\WINCE_OS\myappprograms.htm:

    <html> <a href="mimelist.dll></a> <a
    href="dbpod_quad.dll></a> </html> 

    Content of ...\PALM_OS\myappprograms.htm:

    <html> <a href="mimelist.prc></a> <a
    href="dbpod_quad.prc></a> </html>

    For an example of the above concept in context, see the Master-Detail page example. Different binaries are referenced for Windows Mobile Pocket PC 2003 vs. Palm at the end of the listing for Detail page.