Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separation of semantics service core and RESTful / WebSocket frontends #3

Open
quyin opened this issue Jan 31, 2013 · 2 comments
Open

Comments

@quyin
Copy link
Member

quyin commented Jan 31, 2013

We need to assess the scope of work and have a plan for this.

@ghost
Copy link

ghost commented Jan 31, 2013

What encompasses the service core. Is this theoretically something that oodss was supposed to handle?

Sent from my Windows Phone


From: quyinmailto:[email protected]
Sent: ‎1/‎31/‎2013 4:03 PM
To: ecologylab/bigSemanticsServicemailto:[email protected]
Subject: [bigSemanticsService] Separation of semantics service core and RESTful / WebSocket frontends (#3)

We need to assess the scope of work and have a plan for this.


Reply to this email directly or view it on GitHub:
#3

@quyin
Copy link
Member Author

quyin commented Feb 1, 2013

The core should basically handle extraction, caches, scheduling of downloads, etc.

The main idea here is that we can expose the same set of functionalities and caches / downloaded pages / extracted semantics stores through different interfaces, e.g. RESTful (http based) and OODSS (preferably WebSocket based).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant