RE: [cdt-dev] Minutes Indexer Call

[Doug Schaefer <DSchaefer@xxxxxxx>]

I am not proposing to use EFS in this case. My point is as John C mentions,
to make a headless RCP app based on cdt.core that manages the indexing on
the remote system. That way the parser has the same access to information as
it would running locally.

My concern is that externalizing the parser will add architectural
requirements that may conflict with other requirements we have, such as
using EFS to access files.

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member
http://cdtdoug.blogspot.com
 

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Chris Recoskie
Sent: Friday, July 21, 2006 11:38 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] Minutes Indexer Call

Indexing via EFS is way too slow in the environments we are trying to
facilitate.  In the EFS case, every single file that needs to be parsed has
to be transferred via some potentially slow communications channel just to
be parsed.  If you can deploy a parsing agent on the remote host instead,
the traffic is minimized to a request to parse a set of files and the set
of results of parsing them.  Generally speaking the latter is much more
bandwidth conservative.

===========================

Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt



                                                                           
             Doug Schaefer                                                 
             <DSchaefer@xxxxxx                                             
             m>                                                         To 
             Sent by:                  "CDT General developers list."      
             cdt-dev-bounces@e         <cdt-dev@xxxxxxxxxxx>               
             clipse.org                                                 cc 
                                                                           
                                                                   Subject 
             21/07/2006 11:32          RE: [cdt-dev] Minutes Indexer Call  
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
               "CDT General                                                
             developers list."                                             
             <cdt-dev@eclipse.                                             
                   org>                                                    
                                                                           
                                                                           




I'm just going to pick on one item for now:

   Enable remote indexing by decoupling the parser from the core as much as
   possible.  This way the indexer can be deployed as its own JAR file and
   be run as an agent on the remote system.  Part of this will involve as
   well decoupling the indexer from any hard dependencies on having an
   Eclipse project (although such information should of course be used if
   available).

I understand the requirement is to deal with source code that resides only
on the remote system (mind you it has to be brought locally to edit.)

I don't understand how that requirement drives you to the solution of
extracting parts of the CDT into a separate jar file to be run outside the
context of the eclipse runtime and resources plugins. Going forward we need
to add more knowledge of the CModel to the parser frameworks to allow us to
take advantage of configurations as added by Mikhail S, and to deal with
the
Eclipse File System (EFS) that provide views on the file system for very
large projects.

For offline indexing proposed by Symbian, I can envision invoking the
indexer as a headless RCP application. Could we not do the same in your
environment?

Thanks,
Doug
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev