Skip to main content

Home/ javascript/ Group items tagged networking

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Adildi ldinlio

Building Resilient IP Networks - Cisco Press | Free Ebooks Download - 0 views

www.ebook-x.com/ing-resilient-ip-networks.html

ebook free download ebooks computer programming network networking cisco

shared by Adildi ldinlio on 24 Oct 08 - Cached
  • Adildi ldinlio on 24 Oct 08
     
    Building Resilient IP Networks free download at the best library for free networking ebooks download.
Adildi ldinlio

Create Your Own Home Networks - Sams | Free Ebooks Download - 0 views

www.ebook-x.com/te-your-own-home-networks.html

ebook free download ebooks computer programming network networking

shared by Adildi ldinlio on 24 Oct 08 - Cached
  • Adildi ldinlio on 24 Oct 08
     
    Create Your Own Home Networks free download at the best library for free networking ebooks download.
Mike Chelen

Aptana Jaxer - 0 views

www.aptana.com/jaxer

javascript ajax open source web server

shared by Mike Chelen on 22 Nov 08 - Cached
  • Mike Chelen on 22 Nov 08
     
    # Use your Ajax, HTML, JavaScript and DOM skills server-side # Integrate with databases, file systems, networks and more # Just tag your JavaScript code to run on the server, the client, or both # Easily deploy your Jaxer apps to Aptana Cloud from within Studio
Julian Knight

Automatically Configure Browsers for Proxy - 0 views

nscsysop.hypermart.net/proxypac.html

firefox ie imported delicious javascript network reference

shared by Julian Knight on 29 Aug 08 - Cached
  • Julian Knight on 29 Aug 08
     
    How to set up autoconfigure scripts for various browsers that need to work on different networks/proxies (PROXY.PAC files).
yc c

Ident Engine - 1 views

identengine.com

javascript lib socialnetwork microformats

shared by yc c on 06 Oct 09 - Cached
  • Hussain M Elius on 06 Oct 09
     
    Without much conscious thought, most of us have built identities across the web. We've filled in profiles, uploaded photos, videos, reviews and bookmarks. The Ident Engine uses semantic web API's to bring together these web footprints.
  • yc c on 05 Dec 09
     
    JavaScript library that retrieves and aggregates social profiles from various sites and networks. Currently supports 72 sites and 149 endpoint mappings * 12seconds.tv * 43things.com * 43people.com * backnetwork.com * backtype.com * barcampbrighton3.backnetwork.com * barcamplondon5.backnetwork.com * blip.fm * blip.tv * blogspot.com * blogger.com * brightkite.com * claimid.com * cocomment.com * corkd.com * dconstruct08.backnetwork.com * del.icio.us * digg.com * disqus.com * djangopeople.net * dopplr.com * edenbee.com * emberapp.com * facebook.com * ffffound.com * flickr.com * fotb08.backnetwork.com * fotolog.com * friendfeed.com * getsatisfaction.com * github.com * google.com * hi5.com * huffduffer.com * identi.ca * jaiku.com * jpgmag.com * krop.com * last.fm * linkedin.com * livejournal.com * ufapi.lab.madgex.com * mashed08.backnetwork.com * meetup.com * microformats.org * mybloglog.com * mytvshows.org * mynameise.com * myopenid.com * myspace.com * newsvine.com * odeo.com * orkut.com * picasaweb.google.com * plaxo.com * plazes.com * profilactic.com * readernaut.com * seesmic.com * slideshare.net * stumbleupon.com * technorati.com * threadless.com * timespeople.nytimes.com * tumblr.com * twitter.com * upcoming.yahoo.com * vimeo.com * vox.com * spaces.live.com * yelp.com * youtube.com Content types definitions * Activity * Audio * Bookmarks * Entries * Events * Friends * Friends Status * Images * Interests * Lifestream * None * Profile * Resume * Services * Slides * Status * Video Schemas * Atom * FOAF * None * Rss * XFN * XFN-hCard * hAtom * hCalendar * hCard * hResume
anonymous

SlimerJS - 3 views

slimerjs.org

javascript headless testing browser gecko firefox development

shared by anonymous on 26 Nov 14 - No Cached
  • anonymous on 26 Nov 14
     
    SlimerJS is useful to do functional tests, page automation, network monitoring, screen capture, etc. SlimerJS is similar to PhantomJs, except that it runs on top of Gecko, the browser engine of Mozilla Firefox (specifically, version 31), instead of Webkit, and is not yet truly headless.
Javier Neira

Why REST ? | /var/log/mind - 0 views

blog.dhananjaynene.com/...why-rest

data integration protocols ftp rpc http analysis

shared by Javier Neira on 09 Jun 09 - Cached
  • ‘ls’ or ‘List Directory’
  • ‘cd’or ‘Change Directory’
  • ‘put’ or ‘Upload’
  • ...26 more annotations...
  • you soon realise that every file and directory is uniquely addressable by its fully qualified path (either absolute or relative) and you can refer to each file and directory by its path. You are also aware that a valid path will uniquely resolve to only one directory or file.
  • the server allows you to retrieve the list of subdirectories and files within your current directory. It always shows you the current state of that directory.
  • following elements
  • A shared understanding of where the files will be uploaded, how they will be uniquely named, their specific file extensions (optionally) and the specific format of the file eg.
  • daemon process on the central office computer (the FTP server) which regularly scans the directory, parses each file as it comes it, does the relevant processing on it, and generates the appropriate result files and places them in the appropriate directories using the shared understanding of the directory structure and the file naming convention to communicate back the results of the processing.
  • RPC allowed you to invoke remote procedures by supporting an ability to pass messages which included the message name and the values for all the parameters necessary to be supplied to the message. Unlike FTP which was meant to do data transfer across a network, RPC was geared to do things remotely.
  • FTP required understanding of very few basic verbs (ls, cd, get, put). Thus the training required to understand FTP semantics was far less than that for RPC. This was partially due to the fact that RPC had a programmatic interface.
  • Moreover each time, new procedures were added or parameters added, these required programmatic changes
  • HTTP protoco
  • Unlike FTP and email, this required the authors to understand a new language, but used a simple markup syntax to keep the learning curve to the minimum
  • get/view/download/save a document
  • Along with RPC, these were essentially different technical manifestations of Service Oriented Architecture (SOA) principles.
  • Many services were usually expected to “do something” though quite often some services would simply return the requested data. Usually but not necessarily the services were identified by using ‘verbs’.
  • allow us to use the web to ‘do something’
  • Resource and media types as the basic units
  • Unique resource identifiers
  • Each resource has often one default manually readable representation
  • Each resource representation optionally includes contextually relevant hyperlinks to other resources
  • REST encourages a uniform interface
  • GET, PUT, POST and DELETE
  • Default Rendering
  • a default HTML rendering capability
  • Aspects such as non maintenance of conversational state, greatly increase the scalability of REST applications even if they do incur a minor cost in efficiency (which can be due to repeated redundant communication of data elements, or additional processing requirements due to preclusion of conversation state).
  • is much easier to understand from a data perspective than an invoice processor API.
  • However the simpler, cleaner and minimalistic abstractions often are far more important than feature richness. A point I would want to make in favour of REST even as I admit that conventional SOA technologies are far more feature rich than REST.
  • REST encourages you to view and model your architecture as a set of resources rather than services.
1 - 7 of 7
Showing 20▼ items per page