Experience with XML Parser and HTTPSocket?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Experience with XML Parser and HTTPSocket?

Markus Gaelli-4
Experience with XML Parser and HTTPSocket?

Hi Folks

We are using GemStone 64 2.4.4.3
We don't use Seaside but we need the XML Parser and are about to import it from [1] via GLASS/Monticello.
Is this parser the way to go or are there other parsers available which might be even faster?

Also: We intend to use HTTPSocket from the GLASS appliance. Any experiences there?

Cheers

Markus


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
       
E-mails are not encrypted and cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses.  The sender
therefore does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission.  
If verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities
or related financial instruments.

 
UBS reserves the right to retain all messages. Messages are protected
and accessed only in legally justified cases.
Reply | Threaded
Open this post in threaded view
|

Re: Experience with XML Parser and HTTPSocket?

NorbertHartl
Hi Markus,

On 11.02.2011, at 10:23, <[hidden email]> <[hidden email]> wrote:

Hi Folks

We are using GemStone 64 2.4.4.3
We don't use Seaside but we need the XML Parser and are about to import it from [1] via GLASS/Monticello.
Is this parser the way to go or are there other parsers available which might be even faster?

As far as I know there is only this xml parser available at this time. The version that has been ported to gemstone is slightly out of date to the current xml parser development. But we can expect soon to have an updated version. The xml parser in its newest incarnation is quite good and fast enough. I'm not sure which xml parser is in the monticello directory but you should be safe using/running

Gofer new
   gemsource: 'MetacelloRepository';
   package: 'ConfigurationOfXMLSupport';
   load.

(Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion

that gives version 1.0.5 at the moment

Also: We intend to use HTTPSocket from the GLASS appliance. Any experiences there?

Depends on what you wanna do. <rant> HTTP handling is a mess in smalltalk, completely. HTTPSocket only helps in one shot operations using simple GET or application/x-www-form-urlencoded POST. If you try to do anything more advanced you're lost. Besides the point that there is no good implementation I can say "but there are many of them". </rant>
At the moment I try to circumvent some of the shortcomings of the existent implementations but planning to port the Zinc http components and then base all my work on this. Zinc http mimicks the popular apache http client which at least does proper mime handling to a great extent. 

Hope this helps,

Norbert

Reply | Threaded
Open this post in threaded view
|

Re: Experience with XML Parser and HTTPSocket?

Philippe Marschall
In reply to this post by Markus Gaelli-4
2011/2/11  <[hidden email]>:

> Hi Folks
>
> We are using GemStone 64 2.4.4.3
> We don't use Seaside but we need the XML Parser and are about to import it
> from [1] via GLASS/Monticello.
> Is this parser the way to go or are there other parsers available which
> might be even faster?
>
> Also: We intend to use HTTPSocket from the GLASS appliance. Any experiences
> there?
>
> Cheers
>
> Markus
>
> Visit our website at http://www.ubs.com
>
> This message contains confidential information and is intended only
> for the individual named.  If you are not the named addressee you
> should not disseminate, distribute or copy this e-mail.  Please
> notify the sender immediately by e-mail if you have received this
> e-mail by mistake and delete this e-mail from your system.
>
> E-mails are not encrypted and cannot be guaranteed to be secure or
> error-free as information could be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete, or contain viruses.  The sender
> therefore does not accept liability for any errors or omissions in the
> contents of this message which arise as a result of e-mail transmission.
> If verification is required please request a hard-copy version.  This
> message is provided for informational purposes and should not be
> construed as a solicitation or offer to buy or sell any securities
> or related financial instruments.

I received your mail but am not the named addressee. The mail went to
[hidden email] but I am [hidden email]. How
should I proceed?

Cheers
Philippe
Reply | Threaded
Open this post in threaded view
|

Re: Experience with XML Parser and HTTPSocket?

NorbertHartl

On 11.02.2011, at 12:00, Philippe Marschall wrote:

> 2011/2/11  <[hidden email]>:
>> Hi Folks
>>
>> We are using GemStone 64 2.4.4.3
>> We don't use Seaside but we need the XML Parser and are about to import it
>> from [1] via GLASS/Monticello.
>> Is this parser the way to go or are there other parsers available which
>> might be even faster?
>>
>> Also: We intend to use HTTPSocket from the GLASS appliance. Any experiences
>> there?
>>
>> Cheers
>>
>> Markus
>>
>> Visit our website at http://www.ubs.com
>>
>> This message contains confidential information and is intended only
>> for the individual named.  If you are not the named addressee you
>> should not disseminate, distribute or copy this e-mail.  Please
>> notify the sender immediately by e-mail if you have received this
>> e-mail by mistake and delete this e-mail from your system.
>>
>> E-mails are not encrypted and cannot be guaranteed to be secure or
>> error-free as information could be intercepted, corrupted, lost,
>> destroyed, arrive late or incomplete, or contain viruses.  The sender
>> therefore does not accept liability for any errors or omissions in the
>> contents of this message which arise as a result of e-mail transmission.
>> If verification is required please request a hard-copy version.  This
>> message is provided for informational purposes and should not be
>> construed as a solicitation or offer to buy or sell any securities
>> or related financial instruments.
>
> I received your mail but am not the named addressee. The mail went to
> [hidden email] but I am [hidden email]. How
> should I proceed?

You are right. I hope I didn't do anything illegal. But then replying with fullquoting the original message could be an criminal act already. And to answer your question: I don't know! *facepalm*

Reply | Threaded
Open this post in threaded view
|

Re: Experience with XML Parser and HTTPSocket?

Markus Gaelli-4
In reply to this post by NorbertHartl
Hi Norbert
 
Thanks a lot for this quick and good answers -- and of course thanks for porting the XML Parser in the first place!
 
Cheers
 
Markus
 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Norbert Hartl
Sent: Freitag, 11. Februar 2011 10:46
To: GemStone Seaside beta discussion
Subject: Re: [GS/SS Beta] Experience with XML Parser and HTTPSocket?

Hi Markus,

On 11.02.2011, at 10:23, <[hidden email]> <[hidden email]> wrote:

Hi Folks

We are using GemStone 64 2.4.4.3
We don't use Seaside but we need the XML Parser and are about to import it from [1] via GLASS/Monticello.
Is this parser the way to go or are there other parsers available which might be even faster?

As far as I know there is only this xml parser available at this time. The version that has been ported to gemstone is slightly out of date to the current xml parser development. But we can expect soon to have an updated version. The xml parser in its newest incarnation is quite good and fast enough. I'm not sure which xml parser is in the monticello directory but you should be safe using/running

Gofer new
   gemsource: 'MetacelloRepository';
   package: 'ConfigurationOfXMLSupport';
   load.

(Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion

that gives version 1.0.5 at the moment

Also: We intend to use HTTPSocket from the GLASS appliance. Any experiences there?

Depends on what you wanna do. <rant> HTTP handling is a mess in smalltalk, completely. HTTPSocket only helps in one shot operations using simple GET or application/x-www-form-urlencoded POST. If you try to do anything more advanced you're lost. Besides the point that there is no good implementation I can say "but there are many of them". </rant>
At the moment I try to circumvent some of the shortcomings of the existent implementations but planning to port the Zinc http components and then base all my work on this. Zinc http mimicks the popular apache http client which at least does proper mime handling to a great extent. 

Hope this helps,

Norbert


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
       
E-mails are not encrypted and cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses.  The sender
therefore does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission.  
If verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities
or related financial instruments.

 
UBS reserves the right to retain all messages. Messages are protected
and accessed only in legally justified cases.