Routes used for talks and for tickets should probably be established beforehand. Although it's implicit that with the user hash it's going to be a beer ticket and withouth it's a talk URI, semantics is always a good thing, and we don't need to guarantee both will be served from the same server (although this application is designed specifically for that)
Routes used for talks and for tickets should probably be established beforehand. Although it's implicit that with the user hash it's going to be a beer ticket and withouth it's a talk URI, semantics is always a good thing, and we don't need to guarantee both will be served from the same server (although this application is designed specifically for that)