About variables and arrays

char* webpage[]

is an array of pointers to char. You would access the elements as with any array in C, by supplying an integer expression between the square brackets. E.g.,

extern void SendToBrowser (char* p);

U8 i;

for (i = 0; i < NumLinesInWebHeader; ++i)
    {
    SendToBrowser (webpage[i]);
    }

Chapter 3 of the Keil C User's Guide discusses the memory areas in the 8051 and keywords used to access them. If you want the string constant to reside in program memory, you simply declare it with the "code" memory qualifier thus:

char const code stringConstant[] = "my string";

That is, stringConstant is an array of chars residing in code memory. Given this declaration, the compiler will know to generate instructions to access the program space of the 8051 instead of the data space for this variable.

C programs on traditional workstation-type machines get loaded into RAM from a disk image. The disk image contains a section with values for constants and initialized variables, which are copied into RAM. Clever linkers arrange it so that the loader puts the initialized values in the right addresses for the program to access. It would be unusual (at least) to see a system that tried to dynamically access the disk to read the string constants during operation of the program.

Embedded systems, however, generally load from some sort of ROM (often flash, these days). There has to be a copy of the string constants in the non-volatile storage for them to survive while power is off. Depending on your system, you can mimic the traditional OS process of loading an image containing these constants into RAM, in which case your string constants would be located somewhere in RAM, as well as in the ROM.

If you have read access to your program store, then to save space you might want to simply leave the string constants in ROM and access them there, rather than copying them to RAM and having two copies. With Keil C, declaring the string in "code" space serves this purpose.

Even if you do have read access to your ROM, you might prefer the data in RAM. Often, RAM access time is much faster than flash access time, so if performance matters more than the space, you might copy the string constants to RAM anyway. It just depends on your particular system and its needs.