Hi Marcos, All,
Regarding the usage of IRI in the widget configuration document, I do not know
which speicification is responsible for mandating the IRI normalization.
It is possible that I simply have not yet found the proper existing explanation
to the issue, so if you know it, I would be
[Being in a different time zone (IST), was not able to actively engage on this
thread :(]
There seems to be Update Loss issue here. If the UI thread which is supposed
to enqueue the statements was scheduled out in the middle of a transaction
block. And the background thread got scheduled in,
On Fri, Jul 24, 2009 at 6:51 PM, Nikunj R. Mehtanikunj.me...@oracle.com wrote:
It appears that Database, SQLTransactionCallback,
SQLTransactionErrorCallback, SQLVoidCallback, SQLTransaction,
SQLStatementCallback, and SQLStatementErrorCallback interfaces can all be
eliminated from WebDatabase
(BCC original mailing lists, directing traffic to public-...@w3.org
for IRI issues.
There are no IRI schemes. I'm not sure that the draft makes
this clear, or makes clear that although most other parts of
the IRI syntax extend URI syntax, the scheme is the same, cannot
contain any %xx encoded
