I am trying to learn federated learning. And the fedjax can't install because of some errors. So I have to choose the other framework. But the code of client is in jax, I'm not sure that if it's feasible to use different frameworks between the server and clients.
Related
Is there a way of integrating Zope 2 (2.13.19) using Python 2.6.8 with socket-io ?
I've found https://python-socketio.readthedocs.io/en/latest/ but it doesn't seem to fit the requirement.
Zope contains a traditional HTTP server, but you could write a ZEO client that would use the socketio library and integrate with Zope's transactions.
It seems that at least the version which is using eventlets should be possible to implement under Python 2.7.
https://python-socketio.readthedocs.io/en/latest/intro.html#server-examples
What Plone version are you using?
I used a slightly different approach in the past, to realize this. I was using a small Pyramid app, which was implementing the socketio (similar to the WSGI way of this library) and was subscribing a Redis PubSub channel. Plone was using event handlers to send messages to the Redis channel which would then consumed by the Pyramid app and send to the socket.
This above library should work and the easy way to use it, would be the same way i did, as a WSGI app together with messaging.
Starting with the upcoming Plone 5.2 you can run Plone on WSGI even under Python 3. This might be a better fit, together with the WSGI app which provides the socket.io support.
The library supports also Redis for multi-server support.
Optional support for multiple servers, connected through a messaging queue such as Redis or RabbitMQ.
The integration with Zope transactions is doable, I had to do that for the Redis messages too.
in the community forum is an interesting thread on that topic too:
https://community.plone.org/t/plone-socketio-websockets/6453/14
I work devops for a fairly large company that is in process of transitioning to microservices. This is a new area for most people involved and some of the governing requests seem like bad practice to me but I don't have the expertise to convince otherwise.
The request is to generate a report before deploying that would list any new api/events (Kafka is our messaging service) in a microservice.
The path that's being recommended is for devs to follow a style guide and then scrape the source code during CI/CD pipeline to generate a report that can be compared to previous reports and identify any new apis.
This seems backwards and unsustainable but I've been unable to find another solution that would satisfy their requests. I've recommended deploying to dev first, then using a tracing tool to identify any api changes, or event subscriptions, but they insist on having the report before deploying.
I'm hoping for any advice on best practice to accomplish this.
Tracing and detecting version changes is definitely over engineering. Whats simpler like #zenwraight has mentioned, is to version your APIs. While tracing through services to explore the different versions and schema could be a potential solution, it requires a lot more investment upfront and if thats not the bread and butter of the company, I would rather use a vendor product that might support something like this.
If discovery is a mechanism that is needed, I would recommend something that publishes internal API docs using a tool like Swagger so that you can search if there's an API you can consume.
And finally to support moving to different versions, I would recommend having an API onboarding process for the services so that teams can notify other teams that are using specific versions their services are coming to the end of their lifecycle and they will need to migrate to newer ones.
I am trying to write a framework on top of Mesos and so far I was able to download Mesos for Ubuntu and start a master and slave on a single machine.
I want to build a Mesos framework using Python, should I use the HTTP API or the native API? What is the difference between them?
I was able to find no documentation on the Python native API, except for some examples.
The HTTP API has documentation but no examples on how to use it. Should I be building a web service if I choose to use the HTTP API?
You should use HTTP API
Native API is easiest way to build Mesos Framework. Just include lib in your project and implement interfaces. Although it comes with some limitations:
Native API is no logger extended, new features goes only to HTTP API e.g., Maintenance Mode MESOS-2063
Native API require mesoslib to be available on system. This makes hard coupling between framework and platform it runs on. With HTTP API you can run your framework on any system no needed to load mesoslib.
Documetnation for HTTP API exists here. It's language agnostic. So there are no examples in python, rather raw HTTP requests. But there are some tutorials how to use it. I can recomend one givien by Marco Massenzi at MesosCon EU 2015
Video
Code
Slides
I'm working on the Windows build of a Qt-Widget application. I need to extend my app to interact with a 3rd-party web service that's built on Thrift. I'm not talking about hosting a web service (ie a Thrift-based server); just writing the client to connect to someone else's existing, live Thrift server.
Can anyone provide a checklist of things to integrate Thrift into Qt?
I'm looking for the bits and pieces that need to be installed, and where to get them. I've started the process of trying to get the two to work together, but it seems to be a non-trivial process since Thrift is a *nix-centric library. I was really hoping that there was a static library and some headers for Thrift, like with many other libraries, but this doesn't appear to be the case.
I have only found this: https://issues.apache.org/jira/browse/THRIFT-1348
Didn't look at it myself though yet.
Just curious, if you were to build an instant message client for the Mac what existing API or service would you use to handle the transfer of messages from one user to another? I am looking for something that can be used in conjunction with objective-c and is compatible with other popular messaging services such as MSN, Yahoo, Aim, gtalk, etc. I don't want to host the service, but rather connect to existing services and use their "pipes".
Thanks
There are many Instant messenger protocols out there.
There is a good bet you could find a Java API for which protocol you would like to use like the XMPP Java API.
Or
for C or C++ you could use the libpurple library.
Your question lacks a lot of informations, so it's rather hard to answer. Please add some details on your requirements. What protocols do you need, what functionality, what development language do you use?
As a start:
Adium has been released under the GPL, thus you can use the code in your own projects as long as the license fits your needs.
http://trac.adium.im/
Another option, if you don't want to implement multiple networks but prefer to use a single protocol where the server provides gateways to other networks you can also check out Jabber/XMPP libraries that are available for the mac.
http://www.google.de/search?q=jabber+library+mac&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:de:official&client=firefox-a