Text 2705, 100 rader
Skriven 2005-02-25 10:08:52 av Adam Flinton (1:379/45)
   Kommentar till text 2683 av Ellen K (1:379/45)
Ärende: Re: ESB / XML / Unicode vs 8-bit characters ?
=====================================================
From: Adam Flinton <adam_NO_@_SPAM_softfab.com>

Ellen K wrote:
>>>For stuff I will have to generate, the FOR XML clause doesn't have a
>>>parameter for the encoding and I'm not finding anything in BooksOnline
>>>about how to set the encoding, or about a default encoding for output
>>>generated using FOR XML.  ???   Clearly this is something about which I
>>>need to learn much more, until now I have only been consuming XML, not
>>>outputting it.   Somewhere I saw that SS2005 can automatically create
>>>SOAP objects, maybe that is something to investigate.
>>>
>>
>>Beware of automatically producing Soap objects as sometimes you have to
>>create more than you need (e.g. if there is a schema).
>
>
> Yes, in general I hate using anything that claims it can automatically do
stuff
> that really is better off being coded.  So far I haven't seen any API's for
> creating Sonic messages, that is what I need to be able to do.  (Have you
> worked with Sonic?)
>

Yup. Via JMS. You create text/string & then set that as the payload (or you get
payload & set it as text/string.


>
>>It is string. Treat it as string. get an api which can read string & an
>>api which can write string.
>
>
> That's what we have been doing internally, but as Rich correctly pointed out,
> really we are creating the documents in whatever encoding VB6 uses, probably
> Windows-1252, even though we are indicating in the header UTF-8 or UTF-16.
Is
> there a way to treat it as string AND control the ACTUAL encoding?
>

Yes. But I do that in java & WRT VB6 I don't know.


>
>>You could move the processing "off shore" to an app server (e.g.
>>apache/IIS/Jboss/Tomcat) & use the db just as a store of tables.
>>A pre-processor so to speak.
>
>
> I have thankfully nothing to do with this part.  The amount of stuff I will
> have to produce (as opposed to consuming) will be relatively small.  I only
> know two pieces I will have to generate:
> 1.We are keeping the leads distribution piece in house, I will have to create
a
> Sonic message that carries each new set of leads to SalesForce.  Also it
looks
> like customer history will only be maintained in the data warehouse, so 2.  I
> will also have to create a Sonic message to deliver history of any given
> customer upon request.
>

Std stuff then. The only interest is where you are putting the
event/logic/action code. If in triggers in the DB I would suggest creating
messaging tables where an event (inc event data) is posted to & tie triggers to
them.

>
>>You can then put a bunch in as pizza boxes & use a load balancer.
>
>
> Also thankfully not my responsibility.
>
>
>>>
>>
>>UTF-8 is the std.
>
>
> Not for Oracle, Oracle 9.x defaults to UTF-16, and we are stuck with that
> because we are using Oracle G/L, A/P and Inventory.  But as previously noted
I
> think forcing every character to 16 bits is likely to negatively impact
> performance.  I have recommended that we test every system's output as input
to
> every other system and then decide.  I'm guessing maybe we can use UTF-8 for
> most things, and only use UTF-16 for those things where UTF-8 doesn't work
> correctly for whatever reason.
>
> Any other ideas and/or information gratefully appreciated!
>

http://www.unicode.org/iuc/iuc18/papers/b1.ppt

http://www.unicode.org/iuc/iuc18/papers/a12.ppt

What version of Oracle is it?

Adam

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)