You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Scott Morgan <sc...@adligo.com> on 2015/02/07 22:05:44 UTC
AWS
Hi,
I have a project which is a Java Async Web Socket Client (AWS). I am
interested in reducing the amount of code I am maintaining and thought that
the HttpComponents group might be a good home for it.
The code is here;
http://cvs.adligo.org/viewvc/aws_client/
It is designed to work with any web socket server, although jetty was the
focus during it's development.
Please let me know if your group is interested in migrating the project
into the Apache space,
and how this is done.
I am in NO rush to make the migration happen, although it would be nice to
get it done by 2018.
Cheers,
Scott
Re: AWS
Posted by Scott Morgan <sc...@adligo.com>.
Hi Oleg,
If there is some sort of incentive (i.e. Adligo (my company) gets
paid), I may be interested. Otherwise I am NOT interested in doing the
grunt work to migrate the project, if I am going to do work on the project
for free I will just keep it in the adligo.org namespace.
I was trying to ask the developers if they had any interest in doing a
re-design/migration.
Cheers,
Scott
On Mon, Feb 9, 2015 at 7:23 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Sat, 2015-02-07 at 15:05 -0600, Scott Morgan wrote:
> > Hi,
> >
> > I have a project which is a Java Async Web Socket Client (AWS). I am
> > interested in reducing the amount of code I am maintaining and thought
> that
> > the HttpComponents group might be a good home for it.
> > The code is here;
> > http://cvs.adligo.org/viewvc/aws_client/
> >
> > It is designed to work with any web socket server, although jetty was the
> > focus during it's development.
> > Please let me know if your group is interested in migrating the project
> > into the Apache space,
> > and how this is done.
> >
> > I am in NO rush to make the migration happen, although it would be nice
> to
> > get it done by 2018.
> >
> > Cheers,
> > Scott
>
> Hi Scott
>
> At present your project has no overlap with HttpComponents code base of
> what so ever. While WebSockets support would make a welcome addition to
> HC, I am not sure a stand-alone project with a completely different
> design and a separate code base is the right way of going about it.
> Would you be personally willing to do all the necessary grunt work to
> re-design and migrate the project?
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
Re: AWS
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sat, 2015-02-07 at 15:05 -0600, Scott Morgan wrote:
> Hi,
>
> I have a project which is a Java Async Web Socket Client (AWS). I am
> interested in reducing the amount of code I am maintaining and thought that
> the HttpComponents group might be a good home for it.
> The code is here;
> http://cvs.adligo.org/viewvc/aws_client/
>
> It is designed to work with any web socket server, although jetty was the
> focus during it's development.
> Please let me know if your group is interested in migrating the project
> into the Apache space,
> and how this is done.
>
> I am in NO rush to make the migration happen, although it would be nice to
> get it done by 2018.
>
> Cheers,
> Scott
Hi Scott
At present your project has no overlap with HttpComponents code base of
what so ever. While WebSockets support would make a welcome addition to
HC, I am not sure a stand-alone project with a completely different
design and a separate code base is the right way of going about it.
Would you be personally willing to do all the necessary grunt work to
re-design and migrate the project?
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org