While this was meant to separate spec concerns between Web Payments and Web Keys, it is not immediately apparent why we need two files. It may be more pure from a design standpoint... but some people may not care and may just want to have the Web Keys endpoint expressed in /.well-known/payswarm since PaySwarm needs it anyway.
Placing it in one file would reduce the number of overall HTTP requests from PaySwarm clients. We can still keep the old /.well-known/web-keys file around, but move its services into /.well-known/payswarm?
Melvin Carvalho noted that it's difficult to understand the differences between the two .well-known endpoints that PaySwarm uses:
http://lists.w3.org/Archives/Public/public-webpayments/2012Aug/0009.html
While this was meant to separate spec concerns between Web Payments and Web Keys, it is not immediately apparent why we need two files. It may be more pure from a design standpoint... but some people may not care and may just want to have the Web Keys endpoint expressed in /.well-known/payswarm since PaySwarm needs it anyway.
Placing it in one file would reduce the number of overall HTTP requests from PaySwarm clients. We can still keep the old /.well-known/web-keys file around, but move its services into /.well-known/payswarm?