Advice to manage "lib and server" for multi module?

[thearabbit]

The firs I am sorry, I known that mantra don't care the module structure in lib, server. But could you advice to manage them for me? For example I have 3 module in client A, B, C, so 1.

lib/
   A_collection1
   A_collection2
   B_collection1
...............
server/
   methods/
      A_method1
      A_method2
      B_method1
..................

2.

lib/
   A/
      collection1
      collection2
   B/
      collection1
...............
server/
   A/
      methods/
         method1
         method1
       ..............
   B/
..................

Which one should I choose (1 or 2)? Thanks for your advice!

[smeijer]

@arunoda and others; there is a lot of request for mantra specifications for the server side. I understand the reason to keep it separated. But can we not make a mantra-meteor extension / chapter, or just a general mantra-backend?

Mantra is a big succes; kadirahq libraries in general are a big succes. So accept it; we need your guidance for the server part. ;-)

[smeijer]

@thearabbit, The server part is not clearly specified in the docs. At least not so clear as the client side. But regarding to directory structure, there is this: Appendix-Server-Side-Directory-Layout

[thearabbit]

Thanks for your reply.