Thanks again, Gunnar. So, from your experience... does it make sense to work on API being more RESTful or not?
If clients are used to using WorkspaceModifyOperation, then porting such clients into a different environment where remote services are in the game may be difficult. If the original (local) API uses other concepts for ensuring ACID, it might be easeir to port such clients into a RESTful world. Or am I misunderstanding, because it doesn't make sense to try and use similar APIs for "local" and "remote" scenarios anyways (as Scott has mentioned)? In other words, would a remote-enabled workspace work totally different than a local one anyways? With a "Remote Workspace Service" offering a totally different (RESTful) API than the local Resource API today. But how would clients then write code which they intend to be using in both Local and Remote workspace scenarios? Would they code against the Remote Service only and have a "local server" translate that into local calls? Cheers, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
