At a second thought , perhaps there could be different servers targeted for several redirects .
Cheers , Alex On 4/17/07, Alexandru Dragomir <[EMAIL PROTECTED]> wrote:
I might be wrong (i haven't worked with phone browsers) but it think is a missunderstanding. The redirections are happening only on the server side. The client only knows of one request and one answer. What is happening on the server - the redirects - are invisible to the client.. Also , there are ways provided so that you don't need the session to store state (see activate/passivate i think) It only comes to the actual "network" overhead which should not be high since is happening inside the server.. True ? ;) Cheers , Alex On 4/13/07, Patrick Moore <[EMAIL PROTECTED]> wrote: > > well at least one reason is that phone browsers ask the user to > confirm each and every client-side redirect > > On 4/12/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > > On 4/12/07, Andreas Pardeike <[EMAIL PROTECTED]> wrote: > > > > > Is that clever design? I can think of several reasons why this could > be > > > a bad idea. What's the reasoning behind this? > > > > Redirects helps you keeping your url and page states cleans, i mean > > helps you a lot. > > Which use case do you think to address? > > > > -- > > Massimo > > http://meridio.blogspot.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
