× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It is an Angular program that is currently using Firebase to store its data.
The call to Firebase does not return chunk data, it returns just the JSON
data.

I am writing an RPGLE/YAJL back end server executed through Apache to
replace the firebase call. The plan was to only swap the URL address. I
don't really want to have to modify all of the Angular calls to strip the
extra characters and I have not found a way in Angular to say this is chunk
data so automatically strip it.

I don't mean to be a jerk with this. I just don't understand why it DOES
work one way with Firebase but it DOESN'T work that same way with
Apache/RPGLE/YAJL. Is Firebase the one that is wrong and doing something
non-standard?



-----Original Message-----
From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brad Stone
Sent: Tuesday, October 18, 2022 9:07 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WEB400] YAJL

Please tell us what you are using to make the request and get the data back.
Did you write some socket application yourself or are you using another
solution?

Whatever that application is, that's the issue. It's not processing the
returned chunked data properly.

On Mon, Oct 17, 2022 at 9:25 PM <smith5646midrange@xxxxxxxxx> wrote:

The program that is receiving the data is expecting pure JSON data to
be returned. Instead is it receiving these extra bytes prior to the
first { and is abending.

-----Original Message-----
From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Scott
Klement
Sent: Monday, October 17, 2022 10:06 PM
To: web400@xxxxxxxxxxxxxxxxxx
Subject: Re: [WEB400] YAJL

The "chunked" part is a normal and expected part of the HTTP protocol.
Can you explain what problem it is causing you?

Since it is part of HTTP, it is being added (correctly) by the IBM
HTTP server and is normal and expected. It won't be in a save-to-file
because that doesn't go through the HTTP server. The data isn't being
added by YAJL, it's just part of the HTTP protocol.

On 10/17/2022 6:34 PM, smith5646midrange@xxxxxxxxx wrote:
Maybe I'm just being dense here but when I pull data from filebase,
it is not chunked. Is this a limitation of Apache or YAJL or why
can't I do it with the IBM i?


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx Before posting, please
take a moment to review the archives at
https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx Before posting, please
take a moment to review the archives at
https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: WEB400@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.