hi !
I was looking at the new NIO client. I don't think we need to use
NbProcessor +1 threads when creating such a client. 2 threads are a
decent default value (not just one, as we may have two messages arriving
in parallel). If the users want more, they can stll provide the number
of threads in t
I just set those value to mimic the MINA 2 behavior, but I think you are
right, it's too much nowadays.
On Wed, Jan 2, 2013 at 11:24 AM, Emmanuel Lécharny wrote:
> hi !
>
> I was looking at the new NIO client. I don't think we need to use
> NbProcessor +1 threads when creating such a client. 2
Infra fixed it, the synchronization was stuck because we changed the mina
trunk location.
On Tue, Jan 1, 2013 at 9:42 AM, Julien Vermillard wrote:
> OK I suppose the next step is to fill a jira issue for infra for starting
> the migration.
>
> Ashish : no idea how it's working, but it's looking
hc has nio based implementation as well
http://hc.apache.org/httpcomponents-core-ga/httpcore-nio/xref/index.html
See nio.codecs package
On Tue, Jan 1, 2013 at 11:53 PM, Julien Vermillard wrote:
> Definitively should take a look.
> The only tricky issue is streaming large content, because MINA
On Mon, Dec 31, 2012 at 12:59 PM, Niklas Gustavsson
wrote:
> On Mon, Dec 31, 2012 at 7:42 AM, Julien Vermillard
> wrote:
>
>> I'm wondering since the website is migrated to the brand new CMS, perhaps
>> we could migrate the code to the new ASF git repo ?
>>
>
> Huge +1. As someone who uses git fo
Ok I'll run a formal vote and then open the infra issue
On Wed, Jan 2, 2013 at 12:36 PM, Bernd Fondermann <
bernd.fonderm...@gmail.com> wrote:
> On Mon, Dec 31, 2012 at 12:59 PM, Niklas Gustavsson
> wrote:
> > On Mon, Dec 31, 2012 at 7:42 AM, Julien Vermillard <
> jvermill...@gmail.com>wrote:
>
Hi,
following the previous git thread, here a formal vote for (or against) the
migration from SVN to GIT of our canonical repos.
[ ] +1 | migrate to git
[ ] ±0 | Abstain
[ ] -1 | do *not* migrate, stay on SVN
[X ] +1 | migrate to git
On Wed, Jan 2, 2013 at 5:54 PM, Julien Vermillard wrote:
> Hi,
> following the previous git thread, here a formal vote for (or against) the
> migration from SVN to GIT of our canonical repos.
>
> [ ] +1 | migrate to git
> [ ] ±0 | Abstain
> [ ] -1 | do *not* migrate, st
Taking a look now. Looks like the code is not really commented :(
On Wed, Jan 2, 2013 at 12:08 PM, Ashish wrote:
> hc has nio based implementation as well
> http://hc.apache.org/httpcomponents-core-ga/httpcore-nio/xref/index.html
> See nio.codecs package
>
>
>
>
> On Tue, Jan 1, 2013 at 11:53 PM
just curious, we have a sandbox folder.. what would happen to it?
On Wed, Jan 2, 2013 at 5:50 PM, Julien Vermillard wrote:
> Ok I'll run a formal vote and then open the infra issue
>
>
> On Wed, Jan 2, 2013 at 12:36 PM, Bernd Fondermann <
> bernd.fonderm...@gmail.com> wrote:
>
> > On Mon, Dec 3
[ ] +1 | migrate to git
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
[X] +1 | migrate to git
On Wed, Jan 2, 2013 at 1:24 PM, Julien Vermillard wrote:
> Hi,
> following the previous git thread, here a formal vote for (or against) the
> migration from SVN to GIT of our canonical repos.
>
> [ ] +1 | migrate to git
> [ ] ±0 | Abstain
> [ ] -1 | do *not* migrate, sta
On Wed, Jan 2, 2013 at 1:24 PM, Julien Vermillard wrote:
> Hi,
> following the previous git thread, here a formal vote for (or against) the
> migration from SVN to GIT of our canonical repos.
[X] +1 | git doit
On Wed, Jan 2, 2013 at 1:24 PM, Julien Vermillard wrote:
> following the previous git thread, here a formal vote for (or against) the
> migration from SVN to GIT of our canonical repos.
>
+1 \o/
/niklas
My idea was to re-used http-core pojo classes like BasicHttpStatus,
BasicHttpResponse, ... in mina-http codec.
In other words don't re-defined Http pojo classes, just implement mina
encoder/decoder
IMO, http-core-nio looks more complex than existing mina-http and
doesn't have clear split between po
15 matches
Mail list logo
