[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Use of BETA in HTTPAPI release
Sometimes, it is called for and the need is to use this. In our case,
we have installed this beta release because of the need for what our
WSDL needed. I don't mind the term as it implies that the code maybe
buggy so to speak. I believe we all need some people who test this
out. I do realize that Scott does have another full time job out side
of this website, plus a family. This tool is a great help regardless
of whether or not the release states beta. I would hate to have to
write this myself.
Ed Waldschmidt, MBA
Sr. Programmer/Analyst
Brotherhood Mutual Insurance Company
260-481-5361
ewaldschmidt@xxxxxxxxxxxxxxxxxxxxx
From: ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Date: 01/24/2012 09:42 AM
Subject: Ftpapi Digest, Vol 67, Issue 35
Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
__________________________________________________________________
Send Ftpapi mailing list submissions to
ftpapi@xxxxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
[1]http://www.scottklement.com/mailman/listinfo/ftpapi
or, via email, send a message with subject or body 'help' to
ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ftpapi digest..."
Today's Topics:
1. HTTPAPI beta (rob@xxxxxxxxx)
2. RE: HTTPAPI beta (Mike Krebs)
3. Re: HTTPAPI beta (Scott Klement)
4. *** HTTPAPI 1.24 Released *** (Scott Klement)
5. Re: HTTPAPI beta (thomas.raddatz@xxxxxx)
6. Re: HTTPAPI beta (Charles Wilt)
7. WSDL2RPG -- unable to create web service test program
(Koester, Michael)
8. RE: *** HTTPAPI 1.24 Released *** (Alvin Strasburger)
----------------------------------------------------------------------
Message: 1
Date: Mon, 23 Jan 2012 17:07:52 -0500
From: rob@xxxxxxxxx
Subject: HTTPAPI beta
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID:
<OF6FB3FF33.8BE093D1-ON8525798E.00792CEE-8525798E.00799290@xxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
The word 'beta' scares one of my coworkers.
[2]http://www.scottklement.com/httpapi/beta/
He is thinking of using WSDL2RPG with some wsdl that the IBM support
team
for their WSDL2RPG tool declared too complex for them.
How long will 1.24 stay 'beta'?
Granted, it is open source, so, technically if there's a bug he should
be
able to work around it, report it in and assist, right?
What's the general feeling out here on using this 'beta'?
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
[3]http://www.dekko.com
-------------- next part --------------
The word 'beta' scares one of my coworkers.
[1][4]http://www.scottklement.com/httpapi/beta/
He is thinking of using WSDL2RPG with some wsdl that the IBM support
team for their WSDL2RPG tool declared too complex for them.
How long will 1.24 stay 'beta'?
Granted, it is open source, so, technically if there's a bug he
should
be able to work around it, report it in and assist, right?
What's the general feeling out here on using this 'beta'?
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
[2][5]http://www.dekko.com
References
1. [6]http://www.scottklement.com/httpapi/beta/
2. [7]http://www.dekko.com/
------------------------------
Message: 2
Date: Mon, 23 Jan 2012 16:33:03 -0600
From: Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>
Subject: RE: HTTPAPI beta
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID: <3DF08BA25872B644A1421B9F085B18298B292D130D@xxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
LOL. In this case...not so scary. How about you refer to it as release
candidate 24 instead? :)
My gut says until the examples get finished? Maybe we could help Scott
finish up the "tutorial" and get this guy promoted.
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[8]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, January 23, 2012 4:08 PM
To: HTTPAPI and FTPAPI Projects
Subject: HTTPAPI beta
The word 'beta' scares one of my coworkers.
[9]http://www.scottklement.com/httpapi/beta/
He is thinking of using WSDL2RPG with some wsdl that the IBM support
team
for their WSDL2RPG tool declared too complex for them.
How long will 1.24 stay 'beta'?
Granted, it is open source, so, technically if there's a bug he should
be
able to work around it, report it in and assist, right?
What's the general feeling out here on using this 'beta'?
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
[10]http://www.dekko.com
------------------------------
Message: 3
Date: Mon, 23 Jan 2012 19:35:59 -0600
From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
Subject: Re: HTTPAPI beta
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID: <4F1E0AFF.5010209@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Rob,
It's "beta" because I decided 3 years ago to overhaul the EXAMPLE
members, but I have been struggling to find time to do that.
HTTPAPIR4 itself is solid. Some of the examples aren't finished.
Maybe I should just release it as-is, and apologize for the unfinished
examples, because otherwise I'm going to keep getting messages like
this.
On 1/23/2012 4:07 PM, rob@xxxxxxxxx wrote:
> The word 'beta' scares one of my coworkers.
> [1][11]http://www.scottklement.com/httpapi/beta/
> He is thinking of using WSDL2RPG with some wsdl that the IBM support
> team for their WSDL2RPG tool declared too complex for them.
> How long will 1.24 stay 'beta'?
------------------------------
Message: 4
Date: Mon, 23 Jan 2012 19:46:30 -0600
From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
Subject: *** HTTPAPI 1.24 Released ***
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID: <4F1E0D76.4050003@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello folks,
The long-awaited version 1.24 of HTTPAPI is now officially released.
[12]http://www.scottklement.com/httpapi/
This release includes the following features/fixes (some of which have
been in beta releases for years, and are heavily tested)
-- Fixes to Cookie handling.
-- Fixes to http_debug file handling
-- Added command-line support
-- Increased size of "addl_header" exit points to 32k
-- Made URL handling more "dummy-proof", similar to browsers.
-- Allow keyring filenames to be specified in https_init()
-- Eliminate 100-continue delays.
-- Allow URL-encoding to work properly with UTF-8
-- Allow longer content-type, user-agent, and soapaction.
-- Allow XML parser to return UCS-2 to your program.
Plus many other bug fixes.
NOTE: Some of the "EXAMPLE" code included in this release is
unfinished.
It's only the EXAMPLEs that aren't finished, the other code is
well-tested. I apologize in advance for any inconvenience this causes.
As always, if you have any problems/questions/concerns, please report
them to the FTPAPI/HTTPAPI mailing list.
[13]http://www.scottklement.com/mailman/listinfo/ftpapi
-SK
------------------------------
Message: 5
Date: Tue, 24 Jan 2012 08:25:37 +0100
From: thomas.raddatz@xxxxxx
Subject: Re: HTTPAPI beta
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Message-ID:
<OFC1D28472.AAED4585-ONC125798F.0028B32A-C125798F.0028CE58@xxxxxx>
Content-Type: text/plain; charset="us-ascii"
... and I am scared about:
"He is thinking of using WSDL2RPG with some wsdl that the IBM support
team
for their WSDL2RPG tool declared too complex for them."
Thomas.
ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx schrieb am 23.01.2012 23:07:52:
> Von: rob@xxxxxxxxx
> An: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Datum: 23.01.2012 23:15
> Betreff: HTTPAPI beta
> Gesendet von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>
> The word 'beta' scares one of my coworkers.
> [14]http://www.scottklement.com/httpapi/beta/
> He is thinking of using WSDL2RPG with some wsdl that the IBM support
team
> for their WSDL2RPG tool declared too complex for them.
>
> How long will 1.24 stay 'beta'?
> Granted, it is open source, so, technically if there's a bug he
should
be
> able to work around it, report it in and assist, right?
>
> What's the general feeling out here on using this 'beta'?
>
>
> Rob Berendt
> --
> Group Dekko
> Dept 1600
> Mail to: 2505 Dekko Drive
> Garrett, IN 46738
> Ship to: Dock 108
> 6928N 400E
> Kendallville, IN 46755
> [15]http://www.dekko.com
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [16]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email confirmation to
the sender.
-------------- next part --------------
... and I am scared about:
"He is thinking of using WSDL2RPG with some wsdl that the IBM support
team
for their WSDL2RPG tool declared too complex for them."
Thomas.
ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx schrieb am 23.01.2012 23:07:52:
> Von: rob@xxxxxxxxx
> An: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Datum: 23.01.2012 23:15
> Betreff: HTTPAPI beta
> Gesendet von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>
> The word 'beta' scares one of my coworkers.
> [1][17]http://www.scottklement.com/httpapi/beta/
> He is thinking of using WSDL2RPG with some wsdl that the IBM
support
team
> for their WSDL2RPG tool declared too complex for them.
>
> How long will 1.24 stay 'beta'?
> Granted, it is open source, so, technically if there's a bug he
should be
> able to work around it, report it in and assist, right?
>
> What's the general feeling out here on using this 'beta'?
>
>
> Rob Berendt
> --
> Group Dekko
> Dept 1600
> Mail to: 2505 Dekko Drive
> Garrett, IN 46738
> Ship to: Dock 108
> 6928N 400E
> Kendallville, IN 46755
> [2][18]http://www.dekko.com
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [3][19]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution,
or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email confirmation to
the sender.
References
1. [20]http://www.scottklement.com/httpapi/beta/
2. [21]http://www.dekko.com/
3. [22]http://www.scottklement.com/mailman/listinfo/ftpapi
------------------------------
Message: 6
Date: Tue, 24 Jan 2012 08:46:00 -0500
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Subject: Re: HTTPAPI beta
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID:
<CAJ=Tnc54K0a_Es0eoLd2CPE27PEa7Hcp8cwQ=FdxNU7TrdYKDQ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1
I'd take "beta" code from Scott over "production" code from anybody
else, myself included.
Charles
On Mon, Jan 23, 2012 at 5:07 PM, <rob@xxxxxxxxx> wrote:
> ? The word 'beta' scares one of my coworkers.
> ? [1][23]http://www.scottklement.com/httpapi/beta/
> ? He is thinking of using WSDL2RPG with some wsdl that the IBM
support
> ? team for their WSDL2RPG tool declared too complex for them.
> ? How long will 1.24 stay 'beta'?
> ? Granted, it is open source, so, technically if there's a bug he
should
> ? be able to work around it, report it in and assist, right?
> ? What's the general feeling out here on using this 'beta'?
> ? Rob Berendt
> ? --
> ? Group Dekko
> ? Dept 1600
> ? Mail to: ?2505 Dekko Drive
> ? ? ? ? ? ? Garrett, IN 46738
> ? Ship to: ?Dock 108
> ? ? ? ? ? ? 6928N 400E
> ? ? ? ? ? ? Kendallville, IN 46755
> ? [2][24]http://www.dekko.com
>
> References
>
> ? 1. [25]http://www.scottklement.com/httpapi/beta/
> ? 2. [26]http://www.dekko.com/
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. ?To unsubscribe, please go to:
> [27]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
>
------------------------------
Message: 7
Date: Tue, 24 Jan 2012 13:53:43 +0000
From: "Koester, Michael" <mkoester@xxxxxxxxxxxxx>
Subject: WSDL2RPG -- unable to create web service test program
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID:
<F6CC4EA8CC70F34BA27EBB20AFC98841012E4D3A@xxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
I'm trying to set up my test program WS_TESTI05, modeled after the
WS000401T, to consume a web service associated with our client's
telecom hardware. I'm using WSDL2RPG 1.15beta4 / 08.01.2012, but am not
able to get past the CRTPGM step due to a big list of errors. Don't
know if our install of WSDL2RPG went badly, or if my development
environment needs to be enhanced with some general authorities that all
real developers get, so I thought I'd start with asking here.
Our IBM i is on 7.1.
I created the following list of module objects and service pgm per the
instructions in the "FAQ How to create a Test Program" (Date:
03.10.2011, Version: 1.5). I specified DIM(*NOMAX) when generating
both WS_INVEN and WS_INVEN05 stubs. I used the program generator to
generate the test pgm source.
Got these okay...
Object Type Library Attribute
WS_INVEN *MODULE MKOESTER RPGLE
WS_INVEN *SRVPGM MKOESTER RPGLE
WS_INVEN05 *MODULE MKOESTER RPGLE
WS_TESTI05 *MODULE MKOESTER RPGLE
...but on my attempt to create the test pgm, I get the following:
CRTPGM PGM(mkoester/ws_testi05)
MODULE(mkoester/ws_testi05)
BNDSRVPGM(mkoester/WS_INVEN) ACTGRP(*NEW)
TEXT('Get NMS Inventory Object Names')
*SRVPGM object QZDMMDTA in library QSOC not found.
Definition not found for symbol 'WSDL2R82_Array_add'.
Definition not found for symbol 'WSDL2R82_Array_get'.
Definition not found for symbol 'WSDL2R82_Array_getName'.
Definition not found for symbol 'WSDL2R82_Array_getNumE'.
Definition not found for symbol 'WSDL2R84_MemoryManager_createArray'.
Not authorized to service program QPMLPMGT in library QSYS.
Not authorized to service program QCSTADMDMN in library QSYS.
Not authorized to service program QCSTCRG1 in library QSYS.
Not authorized to service program QCSTCRG2 in library QSYS.
Not authorized to service program QCSTCRG4 in library QSYS.
Not authorized to service program QCSTCTL in library QSYS.
Not authorized to service program QCSTCTL2 in library QSYS.
Not authorized to service program QCSTDD in library QSYS.
Not authorized to service program QC3KYEXP in library QSYS.
Not authorized to service program QC3KYIMP in library QSYS.
Not authorized to service program QC3MKCLR in library QSYS.
Not authorized to service program QC3MKPLD in library QSYS.
Not authorized to service program QC3MKSET in library QSYS.
Not authorized to service program QC3MKTST in library QSYS.
Not authorized to service program QFPADAP1 in library QSYS.
Not authorized to service program QLPCDROM in library QSYS.
Not authorized to service program QPMAAPI in library QSYS.
Not authorized to service program QSYRGAP1 in library QSYS.
Not authorized to service program QTOQSAPI in library QSYS.
Not authorized to service program QUSRGFA1 in library QSYS.
Not authorized to service program QYPSCOLL in library QSYS.
Not authorized to service program QYPSSRVS in library QSYS.
Not authorized to service program QZCACLT in library QSYS.
Program WS_TESTI05 not created.
My library list includes:
QSYS SYS
QSYS2 SYS
...
QUSRSYS SYS
... SYS
WSDL2RPG USR
LIBHTTP USR
LIBEXPAT USR
MKOESTER USR
... USR
QGPL USR
... USR
QTEMP USR
Please let me know what else I need to provide (unless it's instantly
obvious where this runs amuck).
Many thanks,
Michael Koester
------------------------------
Message: 8
Date: Tue, 24 Jan 2012 09:26:03 -0500
From: "Alvin Strasburger" <alvins@xxxxxxxxxxxxx>
Subject: RE: *** HTTPAPI 1.24 Released ***
To: "'HTTPAPI and FTPAPI Projects'" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID: <008601ccdaa4$1af77b20$50e67160$@com>
Content-Type: text/plain; charset="us-ascii"
We have been running the 1.24 BETA version for almost a year with
absolutely
no issues. Prior to that we ran two previous non-Beta versions with
virtually the same results. It is used hundreds of times each day for
requesting address validation and classification as well as package
carrier
and freight rates. I cannot remember any issues that occurred in our
live
production system. Obviously, we have needed to contact the user group
for
help solving various issues as we developed programs to communicate
with
varying web services.
That said, I wish to sincerely thank Scott for his time and effort
creating,
maintaining and helping troubleshoot this project. In addition I have
one
question. Is the officially released version 1.24 any different than
what we
have been running for the past year? I would assume that if there were
any
changes or additional fixes they would have been released with a higher
version level.
Thanks,
Alvin
Alvin Strasburger
Printgear Sportswear
Phone 803-744-2310
Toll Free 800-763-7763
[28]mailto:alvins@xxxxxxxxxxxxx
[29]www.printgear.com
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[30]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott
Klement
Sent: Monday, January 23, 2012 8:47 PM
To: HTTPAPI and FTPAPI Projects
Subject: *** HTTPAPI 1.24 Released ***
Hello folks,
The long-awaited version 1.24 of HTTPAPI is now officially released.
[31]http://www.scottklement.com/httpapi/
This release includes the following features/fixes (some of which have
been
in beta releases for years, and are heavily tested)
-- Fixes to Cookie handling.
-- Fixes to http_debug file handling
-- Added command-line support
-- Increased size of "addl_header" exit points to 32k
-- Made URL handling more "dummy-proof", similar to browsers.
-- Allow keyring filenames to be specified in https_init()
-- Eliminate 100-continue delays.
-- Allow URL-encoding to work properly with UTF-8
-- Allow longer content-type, user-agent, and soapaction.
-- Allow XML parser to return UCS-2 to your program.
Plus many other bug fixes.
NOTE: Some of the "EXAMPLE" code included in this release is
unfinished.
It's only the EXAMPLEs that aren't finished, the other code is
well-tested.
I apologize in advance for any inconvenience this causes.
As always, if you have any problems/questions/concerns, please report
them
to the FTPAPI/HTTPAPI mailing list.
[32]http://www.scottklement.com/mailman/listinfo/ftpapi
-SK
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[33]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list digest. To unsubscribe, go to:
[34]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
End of Ftpapi Digest, Vol 67, Issue 35
**************************************
------------ IMPORTANT NOTICE ------------
The information in this e-mail and in any attachments
is the property of Brotherhood Mutual Insurance Company
and is confidential. If you are not the intended recipient,
you should delete this message from your system and
immediately notify the sender. Unless otherwise indicated by
Brotherhood Mutual Insurance Company, you may not copy
or send this e-mail or any attachments to any other person
nor disclose the contents to others if such action conveys
confidential information to our competitors or is in any other
way reasonably likely to be adverse to the interests of
Brotherhood Mutual Insurance Company. This e-mail will
not modify any insurance policy term or provision, nor will
it evidence an intent to be bound by or to modify any
contract or agreement.
References
1. http://www.scottklement.com/mailman/listinfo/ftpapi
2. http://www.scottklement.com/httpapi/beta/
3. http://www.dekko.com/
4. http://www.scottklement.com/httpapi/beta/
5. http://www.dekko.com/
6. http://www.scottklement.com/httpapi/beta/
7. http://www.dekko.com/
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. http://www.scottklement.com/httpapi/beta/
10. http://www.dekko.com/
11. http://www.scottklement.com/httpapi/beta/
12. http://www.scottklement.com/httpapi/
13. http://www.scottklement.com/mailman/listinfo/ftpapi
14. http://www.scottklement.com/httpapi/beta/
15. http://www.dekko.com/
16. http://www.scottklement.com/mailman/listinfo/ftpapi
17. http://www.scottklement.com/httpapi/beta/
18. http://www.dekko.com/
19. http://www.scottklement.com/mailman/listinfo/ftpapi
20. http://www.scottklement.com/httpapi/beta/
21. http://www.dekko.com/
22. http://www.scottklement.com/mailman/listinfo/ftpapi
23. http://www.scottklement.com/httpapi/beta/
24. http://www.dekko.com/
25. http://www.scottklement.com/httpapi/beta/
26. http://www.dekko.com/
27. http://www.scottklement.com/mailman/listinfo/ftpapi
28. mailto:alvins@xxxxxxxxxxxxx
29. file://localhost/tmp/www.printgear.com
30. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
31. http://www.scottklement.com/httpapi/
32. http://www.scottklement.com/mailman/listinfo/ftpapi
33. http://www.scottklement.com/mailman/listinfo/ftpapi
34. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------