Skip to main content

Home/ javascript/ Group items tagged integration

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
mahesh 1234

Hibernate Tutorial - javatpoint - 0 views

www.javatpoint.com/hibernate-tutorial

shared by mahesh 1234 on 24 Dec 13 - No Cached
  • mahesh 1234 on 24 Dec 13
     
    Hibernate Tutorial. In this hibernate tutorial, we will learn basics of hibernate, inheritance mapping, collection mapping, component mapping, HQL, HCQL, Named Query, Caching and Integration of Hibernate with other frameworks.
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

Home - chain.js - GitHub - 0 views

github.com/wikis

html javascript jquery programming scripting

shared by Julian Knight on 29 Aug 08 - Cached
  • Julian Knight on 29 Aug 08
     
    JQuery plugin that allows creation of html client-side using templates. Integration with jquery makes the process simple and compatible with events so that DOM manipulation stays consistent. See also interaction.js at http://github.com/raid-ox/interaction.js/wikis. This extends some easy interactions to chain such as drag and drop and sorting. Also usage tutorial at: http://zparse.net.tc/
Julian Knight

Xinha - Trac - 0 views

xinha.webfactional.com

development html javascript programming scripting

shared by Julian Knight on 29 Aug 08 - Cached
  • Julian Knight on 29 Aug 08
     
    Xinha (pronounced like Xena, the Warrior Princess) is a powerful WYSIWYG HTML editor component that works in Mozilla based browsers as well as in MS Internet Explorer. Its configurabilty and extensibility make it easy to build just the right editor for multiple purposes, from a restricted mini-editor for one database field to a full-fledged website editor. Its liberal licence makes it an ideal candidate for integration into any kind of project.
lambdatestteam

End to End Testing - 0 views

www.lambdatest.com/...-know-about-end-to-end-testing

testing softwaretesting manaultesting agile automation technology

shared by lambdatestteam on 13 Dec 18 - No Cached
  • lambdatestteam on 13 Dec 18
     
    End to end testing is a very common testing methodology where the objective is to test how an application works by checking the flow from start to end. Not only the application flow under dev environment is tested, but the tester also has to check how it behaves once integrated with the external interface.
Mike Chelen

Processing 1.0 (BETA) - JSON in Processing - 0 views

processing.org/...YaBB.cgi

json processing

shared by Mike Chelen on 24 Nov 08 - Cached
  • Mike Chelen on 24 Nov 08
     
    Hi. I've just started getting into processing and am really enjoying it -- great work! I'm working on a project that uses data in JSON format (www.json.org). It took me a while to get it going in processing, so I thought I'd post what I did here. If there's a better way (which undoubtedly there is!), please let me know.
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