On Sun, May 16, 2010 at 12:17 PM, Miyuru <miyur...@gmail.com> wrote: > +1 > it will be more convenient and more closer to real user requirements. >
Not exactly. IMO 1 hour is suitable for most production scenarios. In a real system, if an endpoint gets suspended, that usually means something has terribly gone wrong (a backend server may have gone down, a connection may have dropped etc). Recovering from such an error could take a long time. I think the default suspend duration is set to 1 hour considering these issues. But I agree that during development time this could be major pain. In development phase endpoints may get suspended all the time due to various reasons. In that sense it is beneficial to have a much shorter default suspend duration for endpoints. Hence I'm actually +0 on this right now. Thanks, Hiranya > 1 hour is tooooo much. I think 1min is more appropriate. > > > On Sun, May 16, 2010 at 10:17 AM, Supun Kamburugamuva > <supu...@gmail.com>wrote: > >> At the moment default endpoint suspension time is set to 60 * 60 * 1000 >> miliseconds. This means with simple scenarios if a endpoint gets suspended >> user has to restart synapse. How about reducing this default value to lets >> say 30 secs or 1 min? >> >> Thanks, >> Supun.. >> >> -- >> Software Engineer, WSO2 Inc >> http://wso2.org >> supunk.blogspot.com >> >> >> > > > -- > Miyuru Daminda Wanninayaka > Software Engineer - WSO2 Inc. > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
