Alexander, The way we handled a web binding vs. the ³core² service for the ICS was: * We created an (apps) table [4] and wiki page [3] about the ³web app² (.rpps.web) * We created a (plugins) table [6] and wiki page [5] about the core service (.rpps)
So if you agree that this is a good convention, I¹d like to propose the following: * We create and (apps) table [7] and wiki page [8] about the CardSync Web App (.cardsync.web) * We create a (plugins) table [9] and wiki page [10] about the core service (.cardsync) * We pour the content of [1] into [10] * We (you) create [8] If you agree, I will do this immediately. --Paul [1] http://wiki.eclipse.org/CardSync_API [2] http://wiki.eclipse.org/I-Card_Service_Web_App_vs_CardSync_Web_App_Authentic ation [3] http://wiki.eclipse.org/index.php?title=I-Card_Service_Web_App [4] http://wiki.eclipse.org/Components_1.X#I-Card_Service_Web_App [5] http://wiki.eclipse.org/I-Card_Service [6] http://wiki.eclipse.org/Components_1.X#I-Card_Service [7] http://wiki.eclipse.org/Components_1.1#CardSync_Web_App [8] http://wiki.eclipse.org/index.php?title=CardSync_Web_App&action=edit [9] http://wiki.eclipse.org/Components_1.1#CardSync [10] http://wiki.eclipse.org/Components_1.X#CardSync
_______________________________________________ higgins-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/higgins-dev
