On Fri, 2012-04-20 at 12:39 +0200, Michael Stahl wrote:
> >> I'm working on removing SvRefBase from SvParser to make its life cycle
> >> a little more easier to understand. I've checked the call sites of
> >> all of its derived classes, and in most of those call sites, we could
> >> easily replac
On Fri, 2012-04-20 at 13:03 +0200, Eike Rathke wrote:
> Hi Kohei,
>
> On Thursday, 2012-04-19 17:06:43 -0400, Kohei Yoshida wrote:
>
> > My question is, do we need to keep this asynchronicity of
> > SwHTMLParser, or is it okay to change it into a synchronous call like
> > the rest of SvParser use
Hi Kohei,
On Thursday, 2012-04-19 17:06:43 -0400, Kohei Yoshida wrote:
> My question is, do we need to keep this asynchronicity of
> SwHTMLParser, or is it okay to change it into a synchronous call like
> the rest of SvParser uses?
IIRC the intention was to not make the user wait until timeout i
On 20/04/12 09:01, Miklos Vajna wrote:
> On Thu, Apr 19, 2012 at 05:06:43PM -0400, Kohei Yoshida
> wrote:
>> My question is, do we need to keep this asynchronicity of
>> SwHTMLParser, or is it okay to change it into a synchronous call like
>> the rest of SvParser uses?
>
> I would be surprised i
On Thu, Apr 19, 2012 at 05:06:43PM -0400, Kohei Yoshida
wrote:
> My question is, do we need to keep this asynchronicity of
> SwHTMLParser, or is it okay to change it into a synchronous call like
> the rest of SvParser uses?
I would be surprised if this would be really required, all the sw
filter
