Results 1 - 10 of 74,393

Table 1 Standard Services for First PLAN Program

in Specifying the PLAN Network Programming Language
by Pankaj Kakkar , Michael Hicks, Jon Moore, Carl A. Gunter
"... In PAGE 11: ... Active packets based on this service interface do not change the state of routers. The services in Table1 are part of the PLAN standard. Services in Table 2 are not part of the standard yet, but as we gain experience writing more PLAN programs we will be able to decide whether or not to add them to the standard.... ..."

Table 1 Standard Services for First PLAN Program

in Specifying the PLAN Network Programming Language
by Pankaj Kakkar , Michael Hicks, Jon Moore, Carl A. Gunter
"... In PAGE 11: ... Active packets based on this service interface do not change the state of routers. The services in Table1 are part of the PLAN standard. Services in Table 2 are not part of the standard yet, but as we gain experience writing more PLAN programs we will be able to decide whether or not to add them to the standard.... ..."

Table 1 Standard Services for First PLAN Program

in Specifying the PLAN Network Programming Language
by Pankaj Kakkar, Michael Hicks, Jon Moore, Carl A. Gunter
"... In PAGE 11: ... Active packets based on this service interface do not change the state of routers. The services in Table1 are part of the PLAN standard. Services in Table 2 are not part of the standard yet, but as we gain experience writing more PLAN programs we will be able to decide whether or not to add them to the standard.... ..."

Table 1. ZENTURIO service data elements.

in From Web Services to OGSA: Experiences in Implementing an OGSA-based Grid Application
by Radu Prodan
"... In PAGE 4: ... Our WASP implementation not supporting service data exposes Web services state through Java Bean get / set methods, which has the atomicity limitation discussed in [12]. The SDEs elements exported by the OGSI-based ZEN- TURIO services are enumerated in Table1 . The SDEs from the Registry and Factory are implemented by the OGSA toolkit as part of the VORegistry, respectively the Facto- ryServiceSkeleton implementation (the latter as an... In PAGE 5: ... We found this feature as very effective for implementing highly re- sponsive GUI-based clients. In OGSA, users can subscribe for notifications on all SDE changes, described in Table1 (push model). Support for the pull model is offered through findServiceData intro- spection.... ..."
Cited by 1

Table I illustrates the concept of pluggable grid service. The domain specific code is a ray tracer application (code at the left). The pluggable service (remote execution) redirects the execution of render methods to a remote resource. The main point is that the remote execution concern is localized into its own module; it can be plugged into the base scientific code without changing the source code and it can be easily removed from the build (i.e., unplugged). Pluggable services can also be used through code annotations, by introducing the annotation @remoteExec before the render method definition. Annotations are an intermediate approach since they can be ignored (i.e., the functionally they attach can be unplugged), however, they require changes to the source code and they lead to non-localized grid concerns. TABLE I

in Pluggable Grid Services
by João Luís Sobral

Table 1. Risks in service-oriented applications

in Risk Management for Service-Oriented Systems
by Natallia Kokash
"... In PAGE 3: ... 3 Risk Management for Service-Oriented Systems Among a set of risks peculiar for SO systems are risks caused by service providers (disposal of a service, changes in interface and behavioral logics of a service, contract violation, obtrusion of a new contract with worse conditions, disclo- sure of user data) and technical aspects (network or service failures, problems with semantic interoperability). Table1 summarizes some common threats for service-based applications. Security threats (information disclosure, spooflng and tampering, downgrade, repudiation, denial of service, etc.... ..."

Table 1: Comparison of self-adaptive approaches Event Service Aspect

in Self-adaptation of event-driven component-oriented middleware using Aspects of Assembly
by Daniel Cheung-Foo-Wo, Jean-Yves Tigli, Stéphane Lavirotte, Michel Riveill
"... In PAGE 2: ... By event-driven we mean systems notified by significant change, by service-oriented we refer to the architecture based on service descriptions and interactions, and by aspect-oriented we refer to the method- ology enabling separation of concerns. Table1 shows their relative strengths and weaknesses. We see that none can be used alone, but only a combination can meet our event, service, and aspect specifications.... In PAGE 2: ... Aspect-oriented systems provide an enhanced modularity as they include separation of concerns, but are not intended to achieve service collaboration. Table1 reflects the need to integrate all the introduced prin- ciples to build SAPS. We propose our middleware approach... ..."

Table 6 Monetized Benefits From Service Quality Improvements Travel Changes Number Unit Benefits Total Benefits

in author is given attribution. Please send your corrections, comments and suggestions for improving it.
by Todd Litman 2007
"... In PAGE 13: ... For example, assume an urban corridor has 12,000 total daily trips, of which 2,000 are by transit, half of which occur during peak periods. Table6 illustrates the benefits from improving transit service LOS from E to C. These benefits include travel time cost reductions to current transit users (off-peak traveler benefits include no in-vehicle benefits, since these consist largely of reduced crowding, which is a peak period problem), consumer surplus gains to travelers who shift mode (calculated by dividing monetized unit benefits by two, based on the rule-of-half), and reduced external costs (traffic congestion, parking subsidies and accident risk) from reduced driving, estimated at $5.... ..."

Table 2. Parameter changes for assisting neighbors

in Extending network lifetime using an automatically tuned energy-aware mac protocol
by Rebecca Braynard, Adam Silberstein, Carla Ellis 2005
"... In PAGE 9: ... Actions are role-speci c. If a node determines it must assist a neighbor and absorb protocol overhead, it changes its respective a and/or l value based on its communication role and the values in Table2 . These increases allow neighboring nodes to reduce their a and l values to the minimum given a service level.... ..."
Cited by 1

Table 4-1. 2015 Sacramento MEPLAN Scenarios: Percentage Changes From the Base Case

in Applying an Integrated Model to the Evaluation of Travel Demand Management Policies in the Sacramento Region
by Robert A. Johnston, Robert A. Johnston, Caroline J. Rodier, Caroline J. Rodier, John E. Abraham, John E. Abraham, John Douglas Hunt, John Douglas Hunt, Griffith J. Tonkin, Griffith J. Tonkin
"... In PAGE 7: ...able 3-6. Daily Vehicle Emissions Results for the Sacramento Region....................... ......... 29 Table4 -1.... In PAGE 53: ...Land Use and Pricing Policies with the Sacramento MEPLAN Model 43 Travel and Emissions Results In the Pricing amp; Light Rail scenario, there is an increase in mobility over short distances in central zones where light rail service is very good compared to the Base Case. The Sacramento MEPLAN daily mode share results for the 2015 time horizon are presented in Table4 -1. The greater separation of home and work, the availability of high quality rail service, and the increase in auto operating costs serve to increase transit mode share significantly and to reduce drive-alone mode share.... In PAGE 54: ...9% -16.8% Table4 -1. 2015 Sacramento MEPLAN Scenarios: Percentage Changes From the Base Case (Continued) Base (values) Pricing amp; Light Rail TOD, Light Rail, amp; Advanced Transit Pricing, TOD, Light Rail, amp; Advanced Transit... ..."
Results 1 - 10 of 74,393