Sponsored Content
Full Discussion: JavaScript code - UNIX grep?
Top Forums Web Development JavaScript code - UNIX grep? Post 303041015 by Neo on Tuesday 12th of November 2019 09:34:59 AM
Old 11-12-2019
Great.

OBTW, I don't have the exact JSON API output in front of me and your JS code which calls the API, so this might be way off base; but this code seems overly complex to me; but then again, I don't have the JS code which calls the API or example JSON data from the API.

If you want me to take a closer look; please post your JS code which calls the API and some sample JSON output from the API.

Either way, glad you have it working now.

Cheers.
 

8 More Discussions You Might Find Interesting

1. Cybersecurity

Function of Javascript within Unix Network

What attacks can a Unix box get through Javascript? Is the Web Client secure against Javascript attacks if any? Do we have a Trojan horse made in JavaScript? (3 Replies)
Discussion started by: netass
3 Replies

2. Shell Programming and Scripting

clear complex javascript code

Hi, Please advise how can we clear the following javascript content from a file commandline, probably using awk or sed File before removing the content. ################################ root@server1 # cat index.html This is a test page <script language=JavaScript>function d(x){var... (6 Replies)
Discussion started by: fed.linuxgossip
6 Replies

3. UNIX for Dummies Questions & Answers

| help | unix | grep - Can I use grep to return a string with exactly n matches?

Hello, I looking to use grep to return a string with exactly n matches. I'm building off this: ls -aLl /bin | grep '^.\{9\}x' | tr -s ' ' -rwxr-xr-x 1 root root 632816 Nov 25 2008 vi -rwxr-xr-x 1 root root 632816 Nov 25 2008 view -rwxr-xr-x 1 root root 16008 May 25 2008... (7 Replies)
Discussion started by: MykC
7 Replies

4. UNIX for Dummies Questions & Answers

| help | unix | grep (GNU grep) 2.5.1 | advanced regex syntax

Hello, I'm working on unix with grep (GNU grep) 2.5.1. I'm going through some of the newer regex syntax using Regular Expression Reference - Advanced Syntax a guide. ls -aLl /bin | grep "\(x\)" Which works, just highlights 'x' where ever, when ever. I'm trying to to get (?:) to work but... (4 Replies)
Discussion started by: MykC
4 Replies

5. Homework & Coursework Questions

Report on Javascript attacks on Unix

1. The problem statement, all variables and given/known data: Prepare a report discussing from an administration and security perspective, role and function of a JavaScript within a UNIX network. You should illustrate your answer with practical examples. In particular attention should me paid to... (1 Reply)
Discussion started by: afdesignz
1 Replies

6. Shell Programming and Scripting

How to use javascript code in unix shell?

Hi Need help...I have wrritten one code for html through shell scripting in that i am using java scripts to validate some condition and open the html page without clicking the button.... Code Details echo "<script type="text/javascript">" echo "function exec_refresh()" echo "{" ... (4 Replies)
Discussion started by: l_gshankar24
4 Replies

7. Shell Programming and Scripting

How to use JavaScript in UNIX Shell scripting?

I want to navigate through a webpage and save that page in my system local automatically. How can I do that by using JavaScript in a Unix shell script. Any suggestions are welcome! (3 Replies)
Discussion started by: abhi3093
3 Replies

8. Web Development

Path to javascript source code at local browsing

Where should I put my javascript source code in order to run it "locally" by file not by http?---not sure this "locally" is the appropriate word here. My test is when my javascript code (test.js) is put in the site default folder as the test.html in /var/www/html both worked as expected with... (2 Replies)
Discussion started by: yifangt
2 Replies
JSON::Any(3pm)						User Contributed Perl Documentation					    JSON::Any(3pm)

NAME
JSON::Any - Wrapper Class for the various JSON classes. VERSION
Version 1.28 SYNOPSIS
This module tries to provide a coherent API to bring together the various JSON modules currently on CPAN. This module will allow you to code to any JSON API and have it work regardless of which JSON module is actually installed. use JSON::Any; my $j = JSON::Any->new; $json = $j->objToJson({foo=>'bar', baz=>'quux'}); $obj = $j->jsonToObj($json); or $json = $j->encode({foo=>'bar', baz=>'quux'}); $obj = $j->decode($json); or $json = $j->Dump({foo=>'bar', baz=>'quux'}); $obj = $j->Load($json); or $json = $j->to_json({foo=>'bar', baz=>'quux'}); $obj = $j->from_json($json); or without creating an object: $json = JSON::Any->objToJson({foo=>'bar', baz=>'quux'}); $obj = JSON::Any->jsonToObj($json); On load, JSON::Any will find a valid JSON module in your @INC by looking for them in this order: JSON::XS JSON JSON::DWIW And loading the first one it finds. You may change the order by specifying it on the "use JSON::Any" line: use JSON::Any qw(DWIW XS JSON); Specifying an order that is missing one of the modules will prevent that module from being used: use JSON::Any qw(DWIW XS JSON); This will check in that order, and will never attempt to load JSON::Syck. This can also be set via the $ENV{JSON_ANY_ORDER} environment variable. JSON::Syck has been deprecated by it's author, but in the attempt to still stay relevant as a "Compat Layer" JSON::Any still supports it. This support however has been made optional starting with JSON::Any 1.19. In deference to a bug request starting with JSON 1.20 JSON::Syck and other deprecated modules will still be installed, but only as a last resort and will now include a warning. use JSON::Any qw(Syck XS JSON); or $ENV{JSON_ANY_ORDER} = 'Syck XS JSON'; WARNING: If you call JSON::Any with an empty list use JSON::Any (); It will skip the JSON package detection routines and will die loudly that it couldn't find a package. DEPRECATION
The original need for JSON::Any has been solved (quite some time ago actually). If you're producing new code it is recommended to use JSON.pm which will optionally use JSON::XS for speed purposes. JSON::Any will continue to be maintained for compatibility with existing code, and frankly because the maintainer prefers the JSON::Any API. METHODS
"new" Will take any of the parameters for the underlying system and pass them through. However these values don't map between JSON modules, so, from a portability standpoint this is really only helpful for those parameters that happen to have the same name. This will be addressed in a future release. The one parameter that is universally supported (to the extent that is supported by the underlying JSON modules) is "utf8". When this parameter is enabled all resulting JSON will be marked as unicode, and all unicode strings in the input data structure will be preserved as such. Also note that the "allow_blessed" parameter is recognised by all the modules that throw exceptions when a blessed reference is given them meaning that setting it to true works for all modules. Of course, that means that you cannot set it to false intentionally in order to always get such exceptions. The actual output will vary, for example JSON will encode and decode unicode chars (the resulting JSON is not unicode) whereas JSON::XS will emit unicode JSON. "handlerType" Takes no arguments, returns a string indicating which JSON Module is in use. "handler" Takes no arguments, if called on an object returns the internal JSON::* object in use. Otherwise returns the JSON::* package we are using for class methods. "true" Takes no arguments, returns the special value that the internal JSON object uses to map to a JSON "true" boolean. "false" Takes no arguments, returns the special value that the internal JSON object uses to map to a JSON "false" boolean. "objToJson" Takes a single argument, a hashref to be converted into JSON. It returns the JSON text in a scalar. "to_json" "Dump" "encode" Aliases for objToJson, can be used interchangeably, regardless of the underlying JSON module. "jsonToObj" Takes a single argument, a string of JSON text to be converted back into a hashref. "from_json" "Load" "decode" Aliases for jsonToObj, can be used interchangeably, regardless of the underlying JSON module. AUTHORS
Chris Thompson "cthom at cpan.org" Chris Prather "chris at prather.org" Robin Berjon "robin at berjon.com" Marc Mims "marc at questright.com" Tomas Doran "bobtfish at bobtfish.net" BUGS
Please report any bugs or feature requests to "bug-json-any at rt.cpan.org", or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=JSON-Any <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=JSON-Any>. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. ACKNOWLEDGEMENTS
This module came about after discussions on irc.perl.org about the fact that there were now six separate JSON perl modules with different interfaces. In the spirit of Class::Any, JSON::Any was created with the considerable help of Matt 'mst' Trout. Simon Wistow graciously supplied a patch for backwards compat with JSON::XS versions previous to 2.01 San Dimas High School Football Rules! COPYRIGHT &; LICENSE Copyright 2007-2009 Chris Thompson, some rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.3 2011-05-09 JSON::Any(3pm)
All times are GMT -4. The time now is 09:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy