Hello Wappler team and community.
Didn’t find components to integrate into the Wappler projects protocols:
WebDav
CalDAV
CardDAV
Why is this not implemented as Wappler components:
It’s not safe?
Is it not popular?
Hi,
Can you share an example of how a Wappler web app could make use of these protocols?
I have a vague knowledge about these, but haven’t ever had the requirement to use them.
P.S. You can vote for your own requests.
WebDAV — a set of extensions and add-ons to the HTTP protocol that support collaborative work on file editing and file management on remote servers.
Implement in Wappler projects read write update folders and files from cloud servises as Dropbox Yandex Disk and so on.
Server side component connect to file stream servers, Front-End Components get dynamic data for client side display and send POST. Example ajaxbrowser.
Connect and directly manipulate folders and files of almost any cloud service and directly read / write a file from a web page.
CalDAV - Server side component connect to data source link, Front-End Components get dynamic data for client side display and send post.
vCard Extensions to WebDAV ( CardDAV ) is an address book client/server protocol designed to allow users to access and share contact data on a server.
In fact, we can use sources WebDAV as a dynamic server file database, CardDAV as a dynamic Client database, and CalDAV as a dynamic event database.
1 Like
Thank you for the detailed explanation. I don’t understand this completely yet. Will require some practical test on my part to grasp the utility of this.
The work we do on Wappler and the kind of projects we have made so far, have not had a requirement for such functionalities. It could be that our projects might benefit from this, but our lack of knowledge means we did not go down this path.
This is also probably the first time I am seeing this on this community. But from the summarized text you have shared, this does look like a good tool to have in Wappler’s arsenal. +1 from me.
And the way Wappler implements things, it will be a breeze for us devs to use it, without needing to get a deep knowledge/understanding of the underlying complexities.
The protocol is already quite old. MS SharePoint works on this protocol.
If you use Synology NAS this protocol makes it extremely easy and fast to provide your internal collaboration work to frontend in web applications.
Has anyone successfully implemented VCard capability in their applications? I’m looking to replace one of our classic ASP systems with a NodeJS upgrade, one of the main items is the ability to easily share/retain user contact details to a contacts list.
We did it in Classic ASP by writing to a text file and just renaming that file with the VCard extension (.vcf), then it was just a case of pointing a dynamic link to it and the file would open up on the local machines native contact/calendar application.
The markup is simple, here’s a sample:
BEGIN:VCARD
N:Smith;John;
TEL;TYPE=work,VOICE:(111) 555-1212
TEL;TYPE=home,VOICE:(404) 386-1017
TEL;TYPE=fax:(866) 408-1212
EMAIL:smith.j@smithdesigns.com
ORG:Smith Designs LLC
TITLE:Lead Designer
ADR;TYPE=WORK,PREF:;;151 Moore Avenue;Grand Rapids;MI;49503;United States of America
URL:https://www.smithdesigns.com
VERSION:3.0
END:VCARD
I’ve tried some basic testing with the excellent write to file component supplied by @tbvgl - it will write a vcf file like the one above but when I come to open it I’m getting a 500 error saying component doesn’t exist, it looks like my nodejs server is looking for a ‘vcf’ component instead of triggering a file opening.
I’m sure someone must have done it somewhere so I thought I’d see if its possible - any ideas?