Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pekko equivalent? #193

Open
pjfanning opened this issue Mar 6, 2023 · 9 comments
Open

Pekko equivalent? #193

pjfanning opened this issue Mar 6, 2023 · 9 comments

Comments

@pjfanning
Copy link

Would it be possible to consider producing a Pekko equivalent of this lib?

Pekko HTTP is not yet released but snapshot jars can be found at https://repository.apache.org/content/groups/snapshots/org/apache/pekko/

Pekko Connectors is our open source fork of Alpakka and Alpakka contains a connector for aws-spi-akka-http and our plan is to produce Pekko versions of core Alpakka connectors.

@matsluni
Copy link
Owner

matsluni commented Apr 2, 2023

Hi @pjfanning, yes sure I am open to it. What would need to be done for this?

@pjfanning
Copy link
Author

I currently have apache/pekko-connectors#34 (comment) and have a pekko based snapshot ready. If you want, you can take my repo and use it. I will abandon mine if you do so.

@matsluni
Copy link
Owner

matsluni commented Apr 2, 2023

Thanks for your link. Are there discussions or solutions how a library could look like to support both Akka and Pekko? I haven't really followed the discussions what was changed in pekko and what is needed for a library to be compliant also license wise. Is there something what I can read?

@pjfanning
Copy link
Author

I don't think one lib can support both Akka and Pekko. My fork has all the necessary changes to work with Pekko. I created the fork to unblock some work on pekko-connectors - the equivalent of Alpakka.

@jtjeferreira
Copy link
Contributor

I used the approach described here in small internal projects

@matsluni
Copy link
Owner

Hi @pjfanning, sorry for the very slow communication and action on this. If you still want, I can take over.

What would be the best thing todo? I fork your repo and change the maven groupId and publish the current state to maven central?

@pjfanning
Copy link
Author

@matsluni I'm happy for you to take over. You can take my code from https://github.com/pjfanning/aws-spi-pekko-http if it helps. I changed the package names there but you can obviously change them to something that suits you.

When you do a release, I can look at ramping down my project. My project is used in Pekko Connectors and it may not be a good idea for us to switch to your lib until we start setting up the 1.1.0 release. That 1.1.0 release may happen within a month or 2 anyway.

@seveneves
Copy link

Hi @matsluni
What are the latest updates for this issue? what are the maven coordinates of a library to be used a replacement for aws-spi-akka-http?

Hi @pjfanning
can https://github.com/pjfanning/aws-spi-pekko-http be used or is it just temporary solution and will be eventually dropped, ie not maintained?

thanks!

@pjfanning
Copy link
Author

@seveneves my fork is used in Apache Pekko Connectors - it isn't some sort of throwaway project. Yes, https://github.com/pjfanning/aws-spi-pekko-http could possibly be dropped in the future but only if there is a viable alternative lib for users to switch to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants