Sponsored Content
The Lounge What is on Your Mind? Developing Applications for UNIX.COM Post 303028114 by Neo on Monday 31st of December 2018 08:01:00 AM
Old 12-31-2018
Hey Ravinder,
  1. We not going to provide any APIs for backend user data until the current badging system project is done.
  2. Also, you have a lot of learning todo before you go from "zero" to pulling down data via an API and build a vuejs app ("hero"). You need to build some simple apps first and demo some basic ability with the development IDE before getting API data from our server.
  3. And, also before getting API access for back end data, you need to provide me with some some basic plan (what you are going to build) and some example working applications which show you have learned the basics with the VueJS-Bootstrap Node.js IDE.
  4. Then you can get me to write the back end API for you and we will exchange crypto keys for API security Smilie Smilie

You have a lot of badging systems tasks on your plate. Please get those done first before moving to other projects!

Thanks.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

executing applications/commands on a unix server from a windows PC

i have a network drive (samba) mounted on to my PC and also i have SSH client on my machine. however i need to run applications/commands on a unix server from the middle of a different executable(windows compatable one). so i need to connect to the unix server from SSH through the... (1 Reply)
Discussion started by: megastar
1 Replies

2. UNIX for Dummies Questions & Answers

What kind of security applications UNIX and Windows have in common?

Hi guys, may I know what kind of security applications do UNIX and Windows have in common? This is related to a project that is approaching its deadline, so would you all please be kind enough to help me? Thank You. (0 Replies)
Discussion started by: austintham
0 Replies

3. UNIX for Dummies Questions & Answers

developing a Kernel for old old Unix?

Hello all , My father has been running the last version of unix before all the liscensing began 20 or so years ago. In his particular field his programmer has written a great deal of software to work with this version. Emulating so newer computers could speak to the unix server as well. Im sure... (6 Replies)
Discussion started by: Bill78
6 Replies

4. UNIX for Dummies Questions & Answers

How can I rebuild applications that developed in UNIX? I need to use it in windows os with cygwin

I need to rebuild an application that developed in unix environment and run in windows OS with cygwin. so How can I rebuild from the source code? is there any one who said something on this regard? (2 Replies)
Discussion started by: bejirond
2 Replies

5. Shell Programming and Scripting

UNIX command to know the applications

Hi, I have a unix server, I want to know which user applicaions are running on that server. Is there any command ? Thanks (1 Reply)
Discussion started by: nag_sathi
1 Replies

6. UNIX and Linux Applications

Type of UNIX applications

Hello, We are planning a migration from UNIX (HP-UX, AIX, Solaris) to Linux on AZURE. I know it sounds like extremely complicated :( That's why we need your help :) We are at the beggining of stage. We need to categorize the types of applications (software) that generally runs on UNIX... (3 Replies)
Discussion started by: anton.robidson
3 Replies
nns_intro(n)						       Name service facility						      nns_intro(n)

__________________________________________________________________________________________________________________________________________________

NAME
nns_intro - Name service facility, introduction DESCRIPTION
nns (short for nano nameservice) is a facility built for the package comm, adding a simple name service to it. It is also built on top of comm, using it for the exchange of messages between the client and server parts. This name service facility has nothing to do with the Internet's Domain Name System, otherwise known as DNS. If the reader is looking for a package dealing with that please see either of the packages dns and resolv, both found in Tcllib too. Tcllib provides 2 applications and 4 packages which are working together and provide access to the facility at different levels. APPLICATIONS
The application nnsd provides a simple name server which can be run by anybody anywhere on their system, as they see fit. It is also an example on the use of the server-side package nameserv::server. Complementing this server is the nns client application. A possible, but no very sensible use would be to enter name/port bindings into a server from a shell script. Not sensible, as shell scripts normally do not provide a comm-based service. The only case for this to make some sense would be in a shell script wrapped around a Tcl script FOO which is using comm, to register the listening port used by FOO. However even there it would much more sensible to extend FOO to use the nameservice directly. And in regard on how to that nns can be used as both example and template. Beyond that it may also be useful to perform nameservice queries from shell scripts. The third application, nnslog is a stripped down form of the nns client application. It is reduced to perform a continuous search for all changes and logs all received events to stdout. Both clients use the nameserv::auto package to automatically hande the loss and restoration of the connection to the server. PACKAGES
The two main packages implementing the service are nameserv and nameserv::server, i.e. client and server. The latter has not much of an API, just enough to start, stop, and configure it. See the application nnsd on how to use it. The basic client, in package nameserv, provides the main API to manipulate and query the service. An example of its use is the application nns. The second client package, nameserv::auto is API compatible to the basic client, but provides the additional functionality that it will automatically restore data like bound names when the connection to the name service was lost and then reestablished. I.e. it automatically detects the loss of the server and re-enters the data when the server comes back. The package nameserv::common is of no interest to users. It is an internal package containing code and definitions common to the packages nameserv and nameserv::server. All packages use the uevent package for the reporting of special circumstances via events, and reserve the uevent-tag nameserv for their exclusive use. All their events will be posted to that tag. INTERNALS
The document Name service facility, client/server protocol specifies the protocol used by the packages nameserv and nameserv::server to talk to each other. It is of no interest to users of either the packages or applications. Developers wishing to modify and/or extend or to just understand the internals of the nameservice facility however are strongly advised to read it. BUGS, IDEAS, FEEDBACK This document, will undoubtedly contain bugs and other problems. Please report such in the category nameserv of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. Please also report any ideas for enhancements you may have. SEE ALSO
nameserv(n), nameserv::auto(n), nameserv::common(n), nameserv::protocol(n), nameserv::server(n), nnsd(n), nss(n) KEYWORDS
client, name service, server COPYRIGHT
Copyright (c) 2008 Andreas Kupries <andreas_kupries@users.sourceforge.net> nns 1.0 nns_intro(n)
All times are GMT -4. The time now is 05:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy