Tinkering with iCloud, I found out that it is using some tweaked form of WebDAV to store and sync calendars, contacts and bookmarks. I got some specs on CalDAV and CardDAV searching in Google, but for bookmarks Apple seems to have developed its own BookmarkDAV protocol. Is there any documentation on this protocol available?
No, BookmarkDAV is no standard whatsoever.
Related
I've recently been trying to gather a small database of books that I have ISBNs for. My options are limited because I need, among other things, a description, which isn't common in services like this. From what I've gathered, one of the best ways to do this is using Amazon's API.
I've been here where people recommended using Amazon's API, and both there and here they mentioned that the old way used in those answers is now deprecated. Unfortunately, Amazon's own documentation for this thing is horrifically terrible, and I can't seem to find any resources to use it.
Does anyone have tips on what to do, or good places to learn how to do this with Amazon? If there are better alternatives, I'm also glad to take those.
I would go about this in two steps:
use Amazon's API to request the store URL of the book in question
details on the API request from the docs.
Amazon's API won't respond with the description you need, but it will respond with the URL of the page which contains that description. All you'll need to do is crawl that page, perhaps with something like npm crawler.
You'll find the description after the <div id="bookDescription_feature_div" class="feature" data-feature-name="bookDescription"> div of the crawled page.
I am using FB Graph API to get the posts and comments from a Page. Just wanted to know if there is an option to convert the comments /content of any post to required language.
No, Facebook does not offer an API for that.
I am not sure if they are still using Bing for their live translation of content, or have implemented their own system by now. (I think I remember that in the past it used to say below such translations that they were handled through Bing – but that note seems to have gone.)
But using a service such as Bing or Google is probably your best option. (Not sure if they offers APIs for that for free though.)
I've been doing a lot of research for the past few days but it seems I can't arrive with the right answers. And most of the resources are scarce.
Here are my questions, hope you could help me answer it. These questions are all related to Java. On how to access OpenERP 7 data.
Does OpenERP 7 supports RESTFUL and JSON-RPC for Java?
How can we update information and prices for products (in the POS module?)
How we can do a bulk export of all products and prices, without pulling the data one product at a time?
Thank you very much.
-R
There are already available doc for Android app and android internally use Java So may be this can help you
OpenERP Mobile Framework Doc
Thanks
yes openerp support JSON-RPC
from here you can get information
http://doc.openerp.com/trunk/developers/web/rpc/
I've done a simple example using json-rpc on android with android-json-rpc api, to fetch partners through http and https (using self-signed certificate) : https://bitbucket.org/petrus-v/openerpconnection
I haven't found good documentation about openerp low-level json-rpc api, my way was to understand request done with openERP client using any good browser's debbuger.
Hope it's help
You can refer to the official doc website from here
you could always look at wrapper libs for xml-rpc like OERPLib and port them to java
I know this may sound like a stupid question, but numerous google searches haven't given me the answer I'm looking for. I see a lot of data on how to format emails based on Sitecore Templates etc, but nothing on actually sending mail. Do I need to do this via .net code, or does Sitecore have a component that manages sending mail?
Take a look at Sitecore.MainUtil.SendMail as a built in function within Sitecore to send email. My understanding is it uses the standard .net mail library, but puts a Sitecore wrapper around it.
It depends on the volume of mail you want to send. If you just want to send simple emails (ie alert emails or 'thank you for registering' type emails then you would just use the normal built-in .NET email functionality.
For more complicated (campaign/mass) emailing there are add-on modules such as the Email Campaign Manager (ECM) - http://sdn.sitecore.net/Products/ECM.aspx or http://www.sitecore.net/unitedkingdom/Resources/brochures/Sitecore%20Email%20Campaign%20Manager
Sitecore provides some example auto-emailer actions in the 'Sample Workflow' that comes with the default Sitecore install too.
The Web forms for Marketers module also has some emailing actions that are included with the package.
Hope this helps :)
You should probably look into system.mail.net. The best reference site for this can be found here:
http://www.systemnetmail.com/
Thanks for all of the replies.
As with other Sitecore issues, I found that Sitecore was not necessary to solve this issue. Standard .Net functionality did what I wanted much easier.
Does anybody know a wiki engine that can be built on top of a RESTful application?
I have a restful application, that exposes a document resource,
I want the wiki engine to use the REST API to persist the documents, instead of saving them to a DB.
I am also open for suggestions of an open-source wiki engines that can be easily modified to support such functionality.
As Wikis were originally designed to work in a standard browser, and most browsers did not support anything except GET and POST, REST is not a concept used a lot on the wiki world. However, nowadays, some wikis (foswiki - the community fork of TWiki for instance) provide you a REST API to it http://foswiki.org/System/CommandAndCGIScripts#rest ).
But you need the opposite: a wiki with a customizable backend (storage) that could be plugged on top of a REST storage service. As wikis with a pluggable backend, I know only of pmwiki http://www.pmwiki.org/wiki/PmWiki/PmWiki and foswiki (the open fork of TWiki) http://foswiki.org.
Okay, this is a puzzler. Wikis in general are more or less the canonical example of a RESTful approach. The page name names a resource. What do you want that isn't in, eg, Twiki?
While you could try to find a wiki that can use a REST backend, it may be better to write a small wiki yourself. Because even though a your backend has REST interface, that doesn't mean you can put some other application in front of it.
dokuwiki does not use a database. It is a filesystem based wiki. I don't know its internal code structure but you might be able to use it as your base.