Hi Martin, Yup, I understand your concern. There may also be a better name for "remote workspaces". But yes I was just trying to capture issues around client/server.
Just to be clear, if anybody wants to add to the scope, reword some of the items, organize them differently ... hey, have your way with it! Its why its on the wiki. This was just my attempt at putting some content in the proposal. Its extremely important that it reflects what the group wants to do. Regards, Kevin "Oberhuber, Martin" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 08/14/2008 12:51 PM Please respond to E4 developer list <[email protected]> To "E4 developer list" <[email protected]> cc Subject RE: [eclipse-incubator-e4-dev] "Remote workspaces" on E4Project Proposal? Thanks Kevin. My feeling was just that "Remote Workspaces" was unclear as a scope item of its own. I'm ok with understanding it as related to the Client/Server split. When we start shaping out the Flexible Resources theme more clearly, we might also add some clarifications there as to what respect it might be related or unrelated to remote workspaces. I just wanted to avoid ending up with some scope written down in the project proposal that nobody really cares for -- I do think that the project proposal should have some relation to the work that will eventually be performed because there are owners for items. But it looks like my fear is not relevant since you thought about Client/Server when writing it down. Thanks, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin McGuire Sent: Thursday, August 14, 2008 5:15 PM To: E4 developer list Subject: Re: [eclipse-incubator-e4-dev] "Remote workspaces" on E4Project Proposal? Hi Martin, As I recall it came out of the client/server split discussions http://wiki.eclipse.org/E4/ClientServer. You've hit on a lot of the issues. Underlying all this of course is an assumption that with some web based Eclipse UI I *will* still have a workspace on the server (v.s. say SQL queries to a DB). Its a likely path of investigation. > The answer to my question above likely plays a role in planning the > Flexible Resource theme, and in case there is no clear owner I'd > be in favor of getting rid of the Theme from the Scope. I thought the purpose Scope section is to provide a shape to the set of issues *someone* might work on in the e4 project. It was built up from looking through the summit work area notes. I didn't interpret it as each being a work area with distinct owners. I think that's an organization issue internal to the project. I'd be fine with us removing "Remote Workspaces" if we thought it was out of scope, irrelevant, ambiguous, creating too much overlap with an existing project, or just plain wrong because I misinterpreted the topic discussions. If we remove it from the Scope though we're saying nobody is going to be caring/working on it (not even in the Flexible Resources work), its not our job on e4. If its just about who-does-what, then we should decide that separately. Certainly at present our problem isn't around too many groups wanting to tackle the same problem :) Hope the clarifies. Please let me know if you have a different interpretation. Regards, Kevin "Oberhuber, Martin" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 08/14/2008 07:09 AM Please respond to E4 developer list <[email protected]> To "E4 developer list" <[email protected]> cc Subject [eclipse-incubator-e4-dev] "Remote workspaces" on E4 Project Proposal? Hi all, I just looked into the http://wiki.eclipse.org/E4/Project_Proposal#Scope and found something titled "Remote workspaces". Does anybody have any more details about what this might mean, and who would be caring for it? It could involve a whole lot of very different subitems, like What about the Workspace when E4 is running as client/server app? What about synchronous access and high latency in EFS-shared remote resources? What about "linking" remote resources rather than "including" them in order to optimize refresh on slow remote parts of the workspace? What about access control and monitoring change in remote workspaces? Should a notion of "Shadowing", or caching remote resources with a local copy be part of the Platform? The answer to my question above likely plays a role in planning the Flexible Resource theme, and in case there is no clear owner I'd be in favor of getting rid of the Theme from the Scope. Thanks, -- 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 _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
_______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
