Skip to main content

Home/ javascript/ Group items tagged technology

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
qualitypoint Tech

Job opening for freshers (Engineering/MCA) |QualityPoint Technologies - 0 views

qualitypoint.blogspot.com/...or-freshers-engieeringmca.html

jobs SoftwareDevelopment

shared by qualitypoint Tech on 15 Oct 09 - Cached
  • qualitypoint Tech on 15 Oct 09
     
    Currently we are looking for Software Engineers.\n\nDesired Candidate profile:\n \n* Having Good Technical Knowledge and willing to work hard for learning new technologies.\n\n * Team work.\n * Sincere\n * Good communication skills.\n * Knowledge in PHP/mySql, C# is preferred.\n * Willing to work in any technology.\n * Job location :Chennai and Ottapidaram (Tuticorin District)\n * Experience 0-1 year\n\n
mahesh 1234

JSP Tutorial, JavaServer Pages Technology (JSP) - javatpoint - 0 views

www.javatpoint.com/jsp-tutorial

shared by mahesh 1234 on 24 Dec 13 - No Cached
  • mahesh 1234 on 24 Dec 13
     
    JSP Tutorial - Javatpoint website provides you a complete JSP tutorial with practical programming examples and easy steps using this beginner's tutorial containing basic to advanced knowledge of Java JSP Technology including Form Data, HTTP Request Header, Response Header, Scripting elements, Directive elements, Custom tags, Cookies Handling and Session Tracking.
Mike Chelen

Bespin » Code in the Cloud - 0 views

bespin.mozilla.com

mozilla html bespin editor programming javscript ide web

shared by Mike Chelen on 16 Feb 09 - Cached
  • Mike Chelen on 16 Feb 09
     
    Bespin is a Mozilla Labs experiment on how to build an extensible Web code editor using HTML 5 technology.
marketngedwisor

How to become a Front-end developer in 2019 - 0 views

blog.edwisor.com/...-a-front-end-developer-in-2019

front-end development developers front end engineer frontend salary javascript

shared by marketngedwisor on 03 Aug 19 - No Cached
  • marketngedwisor on 03 Aug 19
     
    Front End Development or Client-Side Development is the practice of coding in technologies like HTML, CSS, and Javascript in a website. The practice involves converting Data into a Graphical Interface for a user to view and interact. Growth in Front-end development is excellent and there are plenteous opportunities available, especially because companies now want their customers to have a good experience while using their Web applications. Want to get hired as a Front End Developer in 2019? Acquire skills in Front End Development, Build live Projects and Get Guaranteed Interviews with edWisor.
qualitypoint Tech

CSS - Workaround for max-width property in IE6 |QualityPoint Technologies - 0 views

qualitypoint.blogspot.com/...nd-for-max-width-property.html

CSS Workaround IE6

shared by qualitypoint Tech on 24 Aug 09 - Cached
  • qualitypoint Tech on 24 Aug 09
     
    Max-width is the property used for limiting the width of the image to predefined value. So it will help to show small sized pictures to display in their original size while resizing the large-sized images into a predefined maximum width.
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.
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.
1 - 7 of 7
Showing 20▼ items per page