Network Object/Resource Explorer
Posted: Wed Apr 08, 2020 4:55 pm
A bit off topic, but I thought you guys might be interested, or have some ideas whether this already exists or not.
Today, I needed to look through a few hundred records in a database looking for a specific scenario in the data, and I was trying to think of a way to do this quickly, rather than write a query and click through each record (the data is stored in an XML field). Normally, I would throw together a quick desktop app or web page with a specific UI for this data set, and click through the data that way. But today that seemed like overkill for something I would probably only use once.
So I started thinking about what existing tools that I already had access to that would allow me to quickly look through large amounts of data fairly quickly. In this case, the data was on a remote server.
I've done a lot of work with XML files, JSON, REST services, web pages, and explorer style treeview/listview desktop applications, so I was trying to think of some way to combine them all into a single package, and re-use pre-existing tools wherever possible.
I've partially implemented both SMB and UPnP clients in the past, which both would allow me to use Windows Explorer to connect and navigate through "folders" containing "items", remotely. I've also seen WebDAV as an option for remotely accessing files. Implementing my own "fake" server using these protocols would partially provide what I'm looking for.
But, ideally, I would want to be able to connect to a server or URL, get a list of folders, navigate to a specific location or "file", open up the file and instead of seeing the contents, I would see all of the properties and values in that object, and I would be able to change them and have those changes reflected on the server.
This is pretty typical for a REST service, but each service is different. There is no standard method for browsing a service, and making changes to resources on that service. You have to know the service details at design time, and build an application for each service.
So SMB, UPnP, WebDAV, FTP, etc. all support the browsing part that I need, but not the viewing and editing of resources. REST provides the viewing and editing of resources, but not the browsing part. Are you guys aware of any existing technology that would cover both of these? If not, which of these (or other protocols) would you use if you wanted the maximum flexibility and widespread adoption?
EDIT: Swagger / OpenAPI is pretty close to what I'm looking for, but I think it's fairly flat, so no navigating through folders, and it also isn't terribly good at viewing and editing large amounts of data. However, I could be wrong.
EDIT2: It looks like WebDAV is exactly what I was looking for. It includes support for browsing files and folders, and viewing and editing file properties. https://en.wikipedia.org/wiki/WebDAV
Today, I needed to look through a few hundred records in a database looking for a specific scenario in the data, and I was trying to think of a way to do this quickly, rather than write a query and click through each record (the data is stored in an XML field). Normally, I would throw together a quick desktop app or web page with a specific UI for this data set, and click through the data that way. But today that seemed like overkill for something I would probably only use once.
So I started thinking about what existing tools that I already had access to that would allow me to quickly look through large amounts of data fairly quickly. In this case, the data was on a remote server.
I've done a lot of work with XML files, JSON, REST services, web pages, and explorer style treeview/listview desktop applications, so I was trying to think of some way to combine them all into a single package, and re-use pre-existing tools wherever possible.
I've partially implemented both SMB and UPnP clients in the past, which both would allow me to use Windows Explorer to connect and navigate through "folders" containing "items", remotely. I've also seen WebDAV as an option for remotely accessing files. Implementing my own "fake" server using these protocols would partially provide what I'm looking for.
But, ideally, I would want to be able to connect to a server or URL, get a list of folders, navigate to a specific location or "file", open up the file and instead of seeing the contents, I would see all of the properties and values in that object, and I would be able to change them and have those changes reflected on the server.
This is pretty typical for a REST service, but each service is different. There is no standard method for browsing a service, and making changes to resources on that service. You have to know the service details at design time, and build an application for each service.
So SMB, UPnP, WebDAV, FTP, etc. all support the browsing part that I need, but not the viewing and editing of resources. REST provides the viewing and editing of resources, but not the browsing part. Are you guys aware of any existing technology that would cover both of these? If not, which of these (or other protocols) would you use if you wanted the maximum flexibility and widespread adoption?
EDIT: Swagger / OpenAPI is pretty close to what I'm looking for, but I think it's fairly flat, so no navigating through folders, and it also isn't terribly good at viewing and editing large amounts of data. However, I could be wrong.
EDIT2: It looks like WebDAV is exactly what I was looking for. It includes support for browsing files and folders, and viewing and editing file properties. https://en.wikipedia.org/wiki/WebDAV