[release] 2.0.0-beta1

[jfarcand]

@rlubke @slandelle Any objection? What is missing is a small documentation update to describe how to hook up the new artifact.

[slandelle]

Go for it, as long as we can keep up breaking stuff before final ;)

[slandelle]

More seriously, here's the things I'd like to work on before 2.0 gets final:

• Netty connection pool
• Multiparts

I'm afraid I won't be able to finish all this before september.

[jfarcand]

@slandelle Agree on all. I will need to find time as well to help...but summer looks extremely busy with AsyncIO so I can't garantee I will be able to do something...

[slandelle]

Same thing here with Gatling. And vacations at last! I'll keep you updated. Regarding connection pool, I'll also have a look at what Ryan is up too on the Grizzly side.

[rlubke]

I'm not quite ready :). After I integrate the new pool, I have to finalize the spdy impl. I'm still working out how to deal with spdy connections and pooling as spdy connections have different requirements.

[rlubke]

Good to go with a beta release on my end.

[jfarcand]

+1

[slandelle]

I'd like to first come up with a solution regarding Netty's ByteBuf allocation/deallocation.

[vmalladi]

Hi Jeanfrancois,

When are you planning to release 2.0.0-beta1?

Thanks
Vamsi

[jfarcand]

@vmalladi No date yet.

[jehrhardt]

Is there any list on what will change with 2.0.0 and what still needs to be done?

[slandelle]

What is the question underneath? Willing to lend a hand? ;)

[jehrhardt]

I am using async-http-client and I would like to know, if 2.0.0 has any benefits for me. Of course, I would also like to help on getting it finished.

[slandelle]

For now, it's more of a technical refactoring than new features.

[jfarcand]

@slandelle @rlubke We may want to release an alpha build to get feedback and see if the community can help testing with early release. WDYT?

[slandelle]

👍 IIRC, someone said he experienced buffer leaks with the new Netty provider but never replied then.

[rlubke]

+1

[rlubke]

@slandelle @jfarcand So, shall we move forward on 2.0?

[slandelle]

@jfarcand Could you give the Netty provider and spin?

[softprops]

It looks snapshots should be deployed to sonatype snapshots but I don't see one for 2.0.0-SNAPSHOT is there a resolve I can add to my resolver chain that will pull in the netty4 provider client? I've got a project that depends on the netty3 provider client that I'd like to upgrade so I don't have 2 netty versions on my classpath.

[slandelle]

@jfarcand 👍 for both 1.7.x branch and master
@softprops I must warn you that AHC 2 Netty 4 support is a WIP, so APIs might change. Moreover, don't use guys use Dispatch?

[softprops]

@slandelle yep. I'm working on upgrading unfiltered's netty bindings to netty4. The tests use dispatch and tubesocks, both thin wrappers around async http client's http and websocket client support respectively.

[slandelle]

@softprops Cool! Will talk with @jfarcand about deploying snapshots on Sonatype. Would also gladly talk with you about the Netty 4 new stuff, like pooled vs unpooled buffers.

[softprops]

Yea. I can't wait until the rest of the community standardizes on the newer netty version. I've been using a combination of this and hopping around githubs source browser for the project.

[jfarcand]

Sound like I can't deploy to Sonatype anymore...hence this is why it stopped working. Fixing that now.

@slandelle So ready to the 2.0.0-beta1 (or better versionniong)?

[softprops]

@jfarcand Have you looked at bintray? It looks like the netty project itself already publishes there. I've been using that as there's a lot less ceremony involved in publishing :)

[slandelle]

@softprops That's only for the tarball. Netty snapshots are on Sonatype.

[wsargent]

Is the SPDY impl related to #50 ?

[slandelle]

@wsargent AHC2 will only support Netty 3 and 4. I'm considering releasing some alpha versions.

[slandelle]

Closing, we're already releasing alpha versions.