Title: Message
Carsten,
I would suspect that the fastest algorithm in this case would be a set of
"if" statements, e.g.,
for (int i = 0; i < length - 10; i++)
if (text[i] == 'X')
{
i++
if (text[i] == 'g')
{
....
if (text[i] == ...)
return
something;
...
}
This should work with practically any token that's doesn't have repeating
characters.
In any case, I do agree with Sasha that the current token looks more like
a typing mistake than anything else, and we should consider something that makes
a bit more sense to developers, like an easily articulated prefix (wsia/wsrp), a
pre-defined character (such as Sasha suggested) or a pre-defined tag (e.g.,
<consumer-link>).
Eilon
-----Original Message-----
From: Carsten Leue
[mailto:]
Sent: Friday, September 06, 2002 5:17
AM
To: Sasha Aickin
Cc: Rich Thompson;
; WSRP (E-mail);
Subject: [wsrp] RE: [wsia]
[wsrp-interfaces] Draft spec v0.5
Hi Sasha.
1. I think that the current intend is to return the markup as
a string. In
this case it would need to be XML encoded
(your first example). I also see
this preferable to
requirng the markup to be XML conformant.
2. When
looking for an appropriate URL rewriting marker I decided to use
plain ASCII charaters for the following reason: the fastest
way to locate a
token to my knowledge is the
Boyer-Moore algorithm if the token consists of
improbable characters (O(N/M), see the summary I sent out earlier).
This
algorithm implies (at least any implementation I
know of) that the parser
holds a table that contains
the number of characters the algorithm can skip
per
character to consider. If we allow UNICODE characters as the input set,
this table becomes incredibly large (too large to be useful
;-).
If I think again then maybe it makes sense to
replace this map by a sparse
map implementation. Do
you have experience with such an approach?
Best regards
Carsten Leue
-------
Dr. Carsten Leue
Dept.8288, IBM Laboratory B鐽lingen , Germany
Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
|---------+---------------------------->
|
| Sasha
Aickin |
|
|
<AlexanderA@plumt|
|
|
ree.com> |
|
|
|
|
| 09/04/2002 11:02
|
|
|
PM
|
|---------+---------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
|
To: Rich Thompson/Watson/IBM@IBMUS,
, ,
"WSRP |
| (E-mail)"
<>
|
|
cc:
|
| Subject:
RE: [wsia] [wsrp-interfaces] Draft spec
v0.5
|
|
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
I have a question about getMarkup. Do we expect the
markup sent back from
the method to be XML-encoded or
not? That is, let's say we want to return
the
markup "Hello, <strong>World</strong>". Does the SOAP
response look
like:
<markup xsi:type="xsd:string">Hello,
<strong>World</strong></markup>
or like:
<markup xsi:type="markup">Hello,
<strong>World</strong></markup>
As currently specified, only the former possibility is
allowed, since
markup is specified with type
xsd:string. I think this is great, because
it
will allow us to send non-XML conformant documents like HTML.
Further,
if we do decide that markup will be sent as
an XML-encoded string, then we
could use XML elements
to specify Consumer side URL rewriting, like so:
<markup xsi:type="xsd:string">Please click <a
href=""<wsia:rewriteURL
type="Action"
navigationState="somestate"/>"
>here≶/a></markup>
If we don't decide to have Consumer URL writing use XML
elements, though, I
think there's another solution
that might be more effective than the
"wsia:QXqKYZJVUWj7G" token. We could use Unicode characters from
one of
the "private use" areas of Unicode
(U+E000-U+F8FF, U+F0000-U+FFFFD, or
U+100000-U+10FFFD). These characters are specifically designed
for private
use by applications, and you can easily
put them into XML with character
entities (e.g.
). Further, since ampersand has an escape character
in XML, you can specify when you send portlet content whether
you are
sending the actual control character or text
that should display as the
control character (e.g.
&#xE123; vs. ).
Cheers,
Sasha.
-----Original Message-----
From: Rich
Thompson [mailto:]
Sent: Friday, August 30, 2002 10:19 AM
To:
;
Subject: [wsia] [wsrp-interfaces] Draft spec v0.5
The doc file has now grown to 11MB ....
(See attached file: Draft Spec v0.5.ZIP)
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
