manifesto | : open_hands : The Open Science Company Manifesto | Awesome List library

Please go through the 12-factors of microservices.

The question to your answer in simple words is, Every microservices is having its isolated database( maybe the dedicated table or in NOSQL it's separate bucket for that microservice). And most important, only that microservice can interact with its databases: all other services must go through that service (e.g. via REST/HTTP or a message bus).

Read this link which gives a detailed explanation.

https://12factor.net/backing-services

See below URL::

https://www.nginx.com/blog/microservices-reference-architecture-nginx-twelve-factor-app/

If there's some way of directly getting those attributes, I don't know.

On converting the FileVisitor API to reactive streams:

The mechanism of reactive streams backpressure is a pull-push model, where a demand is first signaled by downstream (the pull part) and then the upstream is allowed to send no more items than the demand signaled (the push part).

The problem with the FileVisitor API is that there's no way to directly hookup with such control flow mechanism. Once you set it off it just goes calling your callback and not caring too much about anything else.

There's no clean way of bridging this, but one way you could do that is using the Source.queue (https://doc.akka.io/docs/akka/current/stream/operators/Source/queue.html) to isolate that API from the rest of your stream like that:

You can use a list comprehension to iterate through each dict in the list.

Convert each dictionary into a string in each iteration, and use if "corruption" not in str(d).lower() to check to see if the string "corruption" is in the lowercased string. If not, then keep it:

I can log onto the Ejabberd web admin panel no problem

Using HTTP or HTTPS? Check if your web browser reports any problem or doubt about the certificate.

but it doesn't seem to like accepting XMPP connections.

Well, in my understaning, it seems your client rejects the certificate provided by ejabberd because the certificate's declared host doesn't match the host that it is serving.

You can try to login with well known Jabber/XMPP clients, like Gajim or Psi. Maybe those tests give you some more light about the problem.

Well, that example source code is six years old, and ejabberd development API has changed since then. I've updated the example, and this compiles and starts correctly with ejabberd 20.07:

That was the expected behavior. According to the docs:

Result:

res :: integer : Status code (0 on success, 1 otherwise)

0 stand for success and 1 stand for failure, not the opposite.

Underline problem is coming because of below code:

It all depends on the client consuming the ServerResponse. According to the WebFlux docs (https://docs.spring.io/spring-framework/docs/5.2.x/spring-framework-reference/web-reactive.html#spring-webflux) setting up handler functions to return Mono regardless of the number of returned items is the standard way and absolutely fine - as long as the client correctly handles the underlying Flux all is well. My problem arose because I tested the the endpoints using curl, which isn't able to detect the underlying Flux. Using a functional-style enabled client (like org.springframework.web.reactive.function.client.WebClient), the Mono can be de-serialized into a Flux first, enabling all the nice reactive functionality, and making our onNext() events show up.

Client code

Calling the backend like so, de-serializing the ServerResponse into a Flux:

Ahh, I see what you mean. You're right, with current MucSub implementation, there is not way to restrict a subscriber from sending messages to the room.

I've filled an issue explaining the case and providing a patch. With that patch, there's a room configuration that allows subscribers to receive messages but not sending them.

In case you are able to apply the patch, compile and install ejabberd: https://github.com/processone/ejabberd/issues/3222