discovery

I have directories, which contain files named like: test_foo.py Each file is a test case. I would like to 1) Run all the tests in a directory from the command line. I am using unittest2 , since we are running Python 2.5.1. From one of these directories I tried typing this at the command line: python -m unittest2 discover -p 'test_*.py' and several different variants. I get no error, but nothing happens. I was expecting all the tests within all the test cases in that directory to run and get results. 2) I also tried having a script in the directory where I did this: loader = unittest2

I'm writing an application that is able to communicate with my PC. I have used the Bluetooth functionalities of the SDK 2.1. I can find devices, get their MAC address, create an RFCOMM socket, but when I start the connection, I get the following error message. Service discovery failed. Is it because of the UUID , which is not the same on my application and on my PC? How can I get the correct UUID on my PC? If I write a such application, is my Nexus One the client or the server? philDev OK, I got the same problem, but I think I can answer a few of your questions. If your PC opened an SPP Port,

Is there any spec or convention on URL where one should place swagger.json (or whatever name it is agreed) so that public API of my site can be automatically discovered? Updated 19 April 2017: The OpenAPI Wiki answer I gave previously is "for a very very very old version of the spec" . The same source states that for 2.0 the standard is swagger.json , for 3.0 it changes to openapi.json . Original answer: The OpenAPI Wiki recommends using an /api-docs endpoint, at least for server APIs. I've seen several sites in the wild that use that, and it's our shop standard. Hope that helps. How about

网络自动发现 支持自动发现网络设备和服务器（可通过自动配置自动发现服务规则实现）。 支持Agent自动注册。 支持自动发现（Low leveldiscover）实现动态监控项的批量监控（支持自定义）。 自动发现lld机制： 1.获取监控数据 脚本获取的数据格式必须是字典，或者字典的列表，因为zabbix discovery只接收json格式 e.g { "data": [ { "{#S2BACKUP}": "3306" }, { "{#S2BACKUP}": "3305" } ] } 2.调用zabbixdiscovery，创建监控项 调用zabbixdiscovery向server端获取监控项，并且创建监控项 3.调用zabbixsender，数据发送给server 调用zabbixsender，将json格式的监控数据导出为文件中，将文件发送给server端 注意必须将zabbix_agentd.conf中的ServerActive设置为server ip，意思为自动注册的监控数据的接收端 e.g if __name__ == "__main__": logutil.make_logger(base_dir='/var/log/zabbix', level='INFO') ##指定日志目录 parser = argparse.ArgumentParser(description

During the first implementation of the NSDManager using the examples and the tutorial on the developer page , the application successfully started the discovery and found the devices. However now it seems to be broken... When the program is started, after some initialization, the code enters the following method and successfully run: public void discoverServices() { Log.d(TAG, "Initializing discovery on NSD"); mNsdManager.discoverServices( SERVICE_TYPE, NsdManager.PROTOCOL_DNS_SD, mDiscoveryListener); } The log-message is received. After a good while (say approx 5 mins.) this is outputted from

The grand design is the following: There is certain application that gets installed as a Windows Service There may be several of these on the network Each of them exposes some interface to the network (think of it as "remote control" or "configuration" - that kind of thing) Then there is another application that acts as a client for that interface (using same analogies - "remote controller" or "configuration tool") The objective of the latter is to sniff out all instances of the former on the network, display them as a list to the user and allow the user to poke them in different places using

I need to be able to discover the services on the local network (so say I am running a chat application and I want to discover other devices on local network running this chat), but sadly I need to be able to use it on devices with API < 16 (so I cannot use android.net.nsd) I am sure this can be done without using NSD API. Question is how. Any help? There are at least three or four options. You can use TCP or UDP Broadcast address Multicast address Iterate over all adresses in your network HTTP 4 Make use of external server or something like GCM (Google Cloud Messaging) ad.1 and 2 Pros: +Easy

When I want to find a "Big" Web service (WS-*/WSDL based) of required functionality I can simply google for ".... filetype:wsdl" because Google indexes also WSDL definitions. Or I can simply use some registries that already crawled the Web for WSDL definitions for me, e.g. SeekDa.com or ServiceFinder. When I want to find RESTful Web service (RESTful Web API) I may count only on the community, because it is not possible to distinguish between URI of RESTful Web service and other Web resources (e.g. Web sites URLs) and hence any focused crawler cannot tell for 100% sure: this is URI of RESTful

For a SaaS startup I'm involved in, I am building both a RESTful web API and a couple of client apps on different platforms that consume it. I think I've got the API figured out, but now I'm turning to the clients. As I've been reading about REST, I see that a key part of REST is discovery , but there seems to be a lot of debate between two different interpretations of what discovery really means: Developer discovery : The developer hard-codes copious amounts of API details into the client, such as resource URI's, query parameters, supported HTTP methods, and other details that they've