Re: mod_perl/Apache troubles with cell phone

[prev] [thread] [next] [Date index for 2005/03/09]

Assuming the mod_perl works with a normal browser, I would ask this:

   a_ is the mod_perl serving the 'phone' directly, or is there an 
intermediary cache in between (ie, squid proxies to mod_perl or vanilla 
httpd, or a vanilla httpd proxies certain content to mod_perl)

if not, i suggest that you do so.

i put 'phone' in quotes, because most often its not the phone 
requesting data, but a proxy service on the telco's end

from my experience, and I would suggest you do a detailed time analysis 
of requesting content your end -- as phone requests i've seen work like 
this:

10:00:00 am - user visits url on phone
10:00:02 am - telco gets url from phone, processes it
10:00:05 am - telco gets around to requesting the url, because they 
have a backlog of requests from selling a service to 10M people that 
was designed for 1M, and the new servers haven't gotten in yet
10:00:10 am - telco gets the response from the url, because they have 
heavy traffic, and don't have the resources or desire to upgrade 
anytime soon.  content is placed in queue
10:00:20 am - telco starts sending content to the phone
10:00:30 am - phone finishes receiving 'hello, world'

I wish i were kidding.  some people in my office just got the t-mobile 
sidekick, which boasts such great internet connectivity that paris 
hilton can't live without it.
Great connectivity indeed -- it loaded the front page of the NYT in a 
very readable format -- except it took 4minutes to load!




On Mar 9, 2005, at 10:31 AM, Stas Bekman wrote:

> Rodger Castle wrote:
>> I've been pulling my hair out this evening trying to resolve a problem
>> serving content to a cell phone.
>> Phone is a LG VX-4500. I've written a simple handler as a start to 
>> just
>> send "Hello" to the phone along with a Content-Length and Connection:
>> Close header but the phone just times out. With a browser, all is 
>> well.
>> File-based (non mod_perl) content gets to the phone fine, it's only 
>> the
>> mod_perl content that is timing out. I can see the requests coming and
>> going in the logs. It looks like the data just never gets sent back 
>> to the
>> phone.
>
>> Running:
>> Debian Sarge
>> Apache 2.0.52
>> mod_perl2
>> Any thoughts on this would be appreciated.
>
> Rodger, you will need to send me one of those toys if you want me to 
> test it for you :)
>
> Seriously, you provide too little information to work with. Does your 
> modperl setup work with a normal browser? What do you see in error_log 
> and access_log files on those requests? Finally saying, I run 
> mod_perl2, is not a way to report a problem, please take a look at:
> http://perl.apache.org/bugs/
>
>
>
> -- 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas@xxxxxx.xxx http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com