title: Flex Modules vs RSL
body: <p>I'm a little bit confused about when is better to use <strong>Flex Modules</strong> or <strong>RSL libriaries</strong> (in Flex 3.5).</p>
  
  <p>My goal is split my project in several unit projects, so I can test and work separately. Let's assume I have a Customer app and Vendor app. I also have a front-end panel with two buttons. Each button launches Customer app or Vendor app. </p>
  
  <p>These applications make different things. They share some .as functions and common components, too.</p>
  
  <p>I understand that if I make a main project (for user login and to show a first panel) and two modules (customer, vendor) I must have all that components in my Eclipse project, isn't it? </p>
  
  <p>Instead of doing modules, should I create SWC for Vendor and other for Customer app and call from main app by using RSL?</p>
  
  <p>So, which option is more suitable? What do you advise me? Which are the trade-offs of each option?</p>
  
  <p>On the other side, this flex application is integrated with Java through Blaze and ibatis for persistence managment, and hold by a web apache server. I considered also to create independent war files to keep this indpendence, but I thought this do not optimize flex code. I'm right? </p>
  
  <p>Thank you.</p>
  
  <p>Nil</p>