How to work with routing in multimodule applications?

Is there simple way to produce links in multimodule application with 2 or more modules?

I mean:
I want to make simple links with the function \Phalcon\Tag::linkTo(array("auth/login", "Login")). And then, if this function was executed in some controller of the "Admin" module, it produces the link: "http://site.com/admin/auth/login". So this link routes to the "Auth" controller of the Admin module...

And in every link of the "Admin" module I need to write \Phalcon\Tag::linkTo(array("admin/auth/login", "Login"))... but it still not work ^)

Dear Phalcon, maybe you have guidlines how to organize the multimodule application with the front-end and the back-end (without describing each route in \Phalcon\Mvc\Router() and with sharing model's structure for both modules)?

And now the link "http://site.com/adminko" will forward us to backend, where all links on the page will be prefixed with "adminko".
The link "http://site.com" will forward us to frontend, where all links on the page will be not prefixed.
It is very good behavior. But, unfortunately, in this case \Phalcon\Tag::stylesheetLink() and \Phalcon\Tag::javascriptInclude() will not work correctly.

But I have an another problem:
How to redirect the user to the frontend from the backend when the user pressed the link in the frontend with the backend's prefix?
And how to not redirect the user to the frontend from the backend when the user pressed the same link in the backend?

It's all about authorization. I want to authorize my users in the frontend and in the backend with single AuthController that situated in the backend. Now if authorization was success the user forwards to the backend's index page:

Why I can't use baseUri for the module if it solves my problem with prefixing all links on the page?
I really don't want to write such huge links in my app.

Using named url can solve problem with forwarding user from the backend controller to the frontend controller.
But how not to forward the user from the backend to the frontend if authorization was performed in the backend?

The baseUri is also used to generate the paths to static content, if you set your baseUri to /adminko all the javascript and css resources are prepended with the baseUri, /adminko/css/ while they're probably in /css/

And yes, you must use "/" for both modules, a global router for all the modules must be set in the application bootstrap,

Generating URLs from the named routes is optional, in fact, this is a strategy to change your routes at any moment without affecting the application, since all the routes are generated from them. If some day you change the prefix /adminko, it will be changed in the whole application.

But that is up to you, If you don't plan to implement that, you can use the static string routes too:

$this->response->redirect('adminko/users/edit');

Or override the redirect method in the response component to prepend the custom base uri:

Redirect now works correctly, but there is problem with $this->dispatcher->forward(array("for" = "front-index")). Phalcon redirects me to the backend's index page instead of the frontend's index page. I don't use "redirect" in this way because I want to "flash" some messages to the user. Tell me please how to output "smthng" to user in backend and forward him to the frontend?

Thank you!
I tried to do so - to put athorization controller in the backend. But in most cases users must log in to application from the frontend (guests) and from the backend (admins). Algorithms of authorization are identical to both groups of users. So I tried to put in the frontend only forms for authorization with routing links to the backend module. Then I had troubles with "back redirection" to the frontend from the backend's actions...

Here everything is as you would expect, and forward to other modules, and everything else. Here authorization and authentication can be done as individual modules. All can be configured using configuration files. Nothing hardcoded.

@Phalcon Look. perhaps this code will be useful for the next version.
I think it's no problem to add 9 listeners to standard phalcon code.