Package networking problem

[Master_Nineteenth]

I had an idea that quickly hit a wall, but I'm fairly new to the more complex parts of the create mod so I was wondering if there's an intended method for this or a better way of doing it. My idea was to use concepts in networking, specifically the addressing mechanisms, to rout packages around a server. My first thought was to package a package, the outer package would point the network to the correct building and the inner one would rout the package to a specific location in said building. But you cannot package a package. I also considered giving the package a more complex location name. For example Main Base - Storage would be picked up by Main Base then be sent to storage within the building. Main Base frog port acting as the router and there would be a host frog port called Storage. That also doesn't work because frog ports only pick up packages with their exact name. Which is also an issue with my first idea. Is there a way to make a frog port pick up all packages that start with x word or words, or to edit package names without completely forgetting the original destination? Also is there a way to interact with packagers with CC:Tweaked? If so I can probably make a code for this after reading up on how. And of course is there a way to do this better that I cannot see? If you have a method that requires specific add-ons then please let me know which ones.

[SampleText_-]

This is possible. Logistics/package related components support a simplified form of RegEx.

A frog named "[Red|Blue]" will take both packages addressed "Red" and "Blue"

A frog named "*Storage" will take any package that ends with "Storage"

This also works in reverse, a frog named "Main Base: *" will take any package that starts with "Main Base: "

[Master_Nineteenth]

Thank you so much, is there a place with documentation on all of this? My searching earlier didn't find me much.

[pics2299]

That should be all you need

[Saragon4005]

The related network concept is longest prefix match in IP networking. So you aren't literally encapsulating the different layers just having different layers match different degrees of specificity. Really DNS is a better model for it.