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

A better routing programme #201

Open
mzz2017 opened this issue Dec 4, 2020 · 3 comments
Open

A better routing programme #201

mzz2017 opened this issue Dec 4, 2020 · 3 comments

Comments

@mzz2017
Copy link
Contributor

mzz2017 commented Dec 4, 2020

Will you consider routingA?

It has been tested in v2rayA for a long time.

And it is suitable for routing rules.

Actually routingA is discussed and considered by v2fly organization and most people agree it for a new routing format for v2ray-core, but no progress yet because of a cross-language implement expected.

I love glider and I will be glad to add it to glider if you wish.

@mzz2017 mzz2017 changed the title A A better routing programme Dec 4, 2020
@nadoo
Copy link
Owner

nadoo commented Dec 4, 2020

Hi @mzz2017 , I really appreciate your effort on improving glider!

glider intends to be simple so I use the command line flag name as key in config file, and use the simplest config file format.

I've had a quick look at routingA package, it's wonderful, with nice design and elegant codes, but it may make glider more complicated, so I'm afraid that I tend to choose not adding this feature (currently), sorry!

Thanks for your kindly help and understanding!

@nadoo nadoo added the resource label Dec 4, 2020
@mzz2017
Copy link
Contributor Author

mzz2017 commented Dec 4, 2020

POC is coming soon, I think it is not so complicated to use as you imaging, because routingA can be a single file so that be imported by the main config file.

It is just used to be a routing rules file, inbounds and outbounds will not be implemented.

Other any part will not be changed and influenced.

Maybe you can cast a glance.

@github-actions
Copy link

github-actions bot commented Mar 5, 2021

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Mar 5, 2021
@nadoo nadoo added enhancement and removed Stale labels Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants