RubenVerborgh solid-server-architecture issues

RubenVerborgh / solid-server-architecture

Proposed architecture for a Solid server

https://rubenverborgh.github.io/solid-server-architecture/solid-architecture-v1-3-0.pdf

13 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Visualization

#43 chrisSCM closed 3 years ago
2
Feedback on Quota layer

#42 rubensworks closed 4 years ago
4
Feedback on LDP layer

#41 rubensworks closed 4 years ago
2
Feedback on HTTP layer

#40 rubensworks closed 4 years ago
2
Coupling to HTTP

#39 rubensworks closed 4 years ago
3
update fields of Operation interface

#38 michielbdejong closed 4 years ago
6
BodyParser produces a ParsedRequestBody, not just any Representation

#37 michielbdejong closed 4 years ago
1
consider changing requestBody to body

#36 michielbdejong closed 4 years ago
0
Pluggable persistence backends

#35 michielbdejong closed 5 years ago
10
Where are `Slug` headers handled?

#34 michielbdejong closed 4 years ago
4
HttpHandler#handle should return a Promise

#33 michielbdejong closed 5 years ago
2
How does LdpHandler tell Authorizer which ResourceStore to use?

#32 michielbdejong closed 5 years ago
3
Registering triggers for notifications

#31 kjetilk closed 4 years ago
7
ContainmentAwareResourceStore

#30 michielbdejong closed 5 years ago
5
Pod Provider Admin Actions

#29 kjetilk closed 4 years ago
5
User Admin actions

#28 kjetilk closed 4 years ago
2
Non-user data

#27 kjetilk closed 4 years ago
2
Input filter and validation

#26 kjetilk closed 4 years ago
4
ACL cache component

#25 kjetilk closed 5 years ago
3
What modifications are needed for HTTP/2

#24 kjetilk closed 4 years ago
3
The Authorization module needs a reason

#23 kjetilk closed 5 years ago
1
Why not checkAccess?

#22 kjetilk closed 5 years ago
1
Support for conditional requests

#21 michielbdejong closed 5 years ago
14
implicit exact mapping between http verbs and operations, or not?

#20 michielbdejong closed 4 years ago
4
Representation super-class feels a bit esoteric

#19 michielbdejong closed 4 years ago
3
RDF-aware ResourceStore could probably expose `DataSet.match` to AclBasedAuthorizer

#18 michielbdejong closed 4 years ago
3
Consider removing BodyParser

#17 michielbdejong closed 4 years ago
3
More detail about how ResourceStore deals with LDP-BC / LDP-RS / LDP-NR

#16 michielbdejong closed 4 years ago
2
Consider merging TargetExtractor/ResourceIdentifier and PreferenceParser/RepresentationPreferences into one RequestParser/Task object

#15 michielbdejong closed 4 years ago
3
Consider removing OperationFactory

#14 michielbdejong closed 4 years ago
2
Classes to interfaces

#13 RubenVerborgh closed 5 years ago
1
Context and hypermedia in all Solid responses?

#12 pmcb55 closed 5 years ago
8
How doe the proposed architecture relate to the concept of an Auth proxy?

#11 RubenVerborgh closed 5 years ago
9
Can you clarify the use of both 'Resource' and 'Representation' in the ResourceStore interface?

#10 pmcb55 closed 5 years ago
7
Should my code be able to access HTTP headers, cookies, query params?

#9 pmcb55 closed 5 years ago
1
Naming change suggestions

#8 pmcb55 closed 5 years ago
2
Is this architecture compatible with inrupt's pod-server?

#7 michielbdejong closed 5 years ago
2
Is this architecture compatible with Trellis?

#6 michielbdejong closed 5 years ago
8
Is Operation.requiredPermissions an odd-one-out?

#5 michielbdejong closed 5 years ago
7
Does the ResourceStore understand conneg?

#4 michielbdejong closed 5 years ago
10
What does 'representation <- patch' mean?

#3 michielbdejong closed 5 years ago
1
Credentials includes both webId and Origin, right?

#2 michielbdejong closed 5 years ago
1
How do you handle append-only patches?

#1 michielbdejong closed 5 years ago
1