hi Filipe,

My version of ibrowse which is in the works has set_inac_timer implemented as follows:

set_inac_timer(State) ->
    cancel_timer(State#state.inactivity_timer_ref),
    set_inac_timer(State#state{inactivity_timer_ref = undefined},
                   get_inac_timeout(State)).

set_inac_timer(State, Timeout) when is_integer(Timeout) ->
    Ref = erlang:send_after(Timeout, self(), timeout),
    State#state{inactivity_timer_ref = Ref};
set_inac_timer(State, _) ->
    State.

What do you think?

Hi Chandru,

Seems fine to me.
When do you plan to add it to the official, stable release?

If it takes long, I'll add mine to CouchDB, since we plan to release 1.0.2 soon.

cheers

I'll get it done asap. Shouldn't take more than a day or two.

Great! :)
Thanks

Is this connected to this problem I've encountered?
I use the async interface to connect to the twitter stream api, I've set {inactivity_timeout, 120000}. This is what happens:

| now() tupple | Some internal data | Data received
{1289,188418,975924} <<>> <<"\r\n">>
{1289,188448,980026} <<>> <<"\r\n">>
{1289,188478,984936} <<>> <<"\r\n">>
{1289,188508,990110} <<>> <<"\r\n">>
{error,req_timedout}

Even though I receive keepalive data from twitter, after 2minutes ibrowse times-out.

Yes, sounds like it is related. A new release is imminent with a fix.

Yes, that's definitely the same error I was having.

Fixed in ibrowse-2.1.0