Comments (4)
Cool-- I get what you mean now. I think the "null component" pattern is going to be incredibly useful, and if we design and code right, we could potentially make the "null component" in a given role be a convenient supertype for other components in that role. That's been difficult with the AuditService
example, but we're still evolving that section.
from trellis.
Part of this issue will be to write a "null client" that does nothing when emitting an event. This would be for the case where messaging is disabled. It will also mean that the TriplestoreResourceService will no longer accept a null
value for the EventService
parameter. This is all in preparation for supporting CDI (at present, various *Service
implementation constructors will accept null
values for "optional" parameters, but that is problematic for simple JSR 330 @Inject
wiring) and this can all be easily mitigated by writing such "null implementations".
from trellis.
How are we using the term "client" here? It seems like a component that emits messages?
from trellis.
Client is a misnomer; I was thinking of the existing notification service components, each of which wraps a particular client. This "null client" wouldn't have a client at all -- it would be better (as you phrase it) to refer to this as a component. I will update the title of the issue to reflect that.
from trellis.
Related Issues (20)
- Resource type is determined by first link header, as opposed to first Link with rel="type"
- Encode IRIs when used with java.net.URI
- Disallow "unwise" characters from URLs
- Improve support for reserved characters
- Support JSON-LD 1.1 HOT 3
- Replace embedded pgsql test server
- Remove basic auth module
- Rename Event API to Notification
- Remove trellis-specific notification connectors
- Separate reactive API from synchronous API HOT 1
- Upgrade to MicroProfile 4.0
- Client support for NodeJS / other languages? HOT 2
- Positioning / contrast with Jena HOT 8
- 500 response returned from request with Accept: text/html header HOT 2
- Potential misuse of `JsonWebToken` in 2 classes HOT 1
- URI consistency for containers and the trailing slash HOT 1
- Make the `trellis:` constants overwritable
- Specify "MP_JWT_VERIFY_PUBLICKEY" as a requirement or remove the dependency
- Query parameters HOT 1
- Use of mutation testing in trellis - Help needed
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from trellis.