text:
MADISON, Wis., and WALKERSVILLE, Md., November , 2020 — FUJIFILM Cellular Dynamics, Inc., a leading global developer and manufacturer of human induced pluripotent stem cells (iPSC) technologies, and Lonza Walkersville, Inc. (Lonza, a leading global GMP iPSC manufacturer), have entered into a worldwide agreement. The agreement enables drug developers to leverage both companies' expertise and technologies for the generation of iPSCs through licensing agreements.
Under the agreement, FUJIFILM Cellular Dynamics grants Lonza a non-exclusive right to use their patents related to iPSC generation, including episomal vectors and reprogramming factors, for the clinical manufacture and differentiation of iPSC lines for cell therapies. Furthermore, Lonza grants FUJIFILM Cellular Dynamics expanded use of its non-exclusive license to its innovative Nucleofector™ technology, to enable efficient transfection of cells, stem cell and cell lines.
Cell therapies have emerged as a promising treatment modality with the ability to augment, repair, or replace human biology, including organs, tissues and cells. Given their incredible capacity to self-renew and the ability to become many different cell types, iPSCs are a critical material used in the development and manufacture of cell therapies.
"FUJIFILM Cellular Dynamics is a key global player with the technology and expertise in iPSC episomal generation enabling high quality, purity and reproducibility," said Takeshi Yamamoto, chief executive officer, FUJIFILM Cellular Dynamics. "We are pleased to reach this outcome with Lonza to produce iPSC lines to better serve drug developers. We expect to grant additional patent licenses to pharmaceutical and biotech companies to support the growth of available cell therapies."
"As true leaders in our field, both companies came to an agreement which benefits our customers and brings clarity to the industry." said Alberto Santagostino, SVP, Head of Cell and Gene Technologies, Lonza. "It shows our common goal to make high quality iPSC therapies available at affordable cost to our customers. Additionally, we are pleased to expand the license-use of our innovative Nucleofector™ technology granted to FUJIFILM Cellular Dynamics. This agreement further strengthens our leading end-to-end proprietary service offering for iPSCs. In combination with Lonza's L7™ hPSC Culture System and non-viral 4D-Nucleofector™ Transfection Technology, this represents an excellent approach for reprogramming and culturing GMP grade iPSCs"
About FUJIFILM
FUJIFILM Cellular Dynamics, Inc. (FCDI) is a leading developer and manufacturer of human induced pluripotent stem cells (iPSCs) utilized in drug discovery and cell therapies. FCDI is using its expertise in iPSC technologies to develop a robust cell therapeutics pipeline to address unmet medical needs in areas such as age-related macular degeneration, retinitis pigmentosa and immuno-oncology. For its partners, FCDI utilizes its iPSC platform to advance the progress of therapeutic candidates in the clinic and provides contract development and manufacturing (CDMO) services. In addition to cell therapy, FCDI also offers life science research tools including the company's inventoried iCell® products, which are available in almost any cell type and are sourced from multiple cell lines which can be applied for target identification as well as toxicity testing. The company also offers custom cell services and cell banking. FCDI's goal is to leverage the vast utility of iPSCs to advance human health and improve the quality of life for patients around the world.
For more information, please visit: www.FujifilmCDI.com
FUJIFILM Holdings Corporation, Tokyo, Japan, brings cutting edge solutions to a broad range of global industries by leveraging its depth of knowledge and fundamental technologies developed in its relentless pursuit of innovation. Its proprietary core technologies contribute to the various fields including healthcare, highly functional materials, document and imaging products. These products and services are based on its extensive portfolio of chemical, mechanical, optical, electronic and imaging technologies. For the year ended March 31, 2020, the company had global revenues of $21 billion, at an exchange rate of 109 yen to the dollar. Fujifilm is committed to responsible environmental stewardship and good corporate citizenship.
For more information, please visit: https://holdings.fujifilm.com/en
About Lonza
At Lonza, we combine technological innovation with world class manufacturing and process excellence. Together, these enable our customers to deliver their discoveries in the healthcare, preservation, and protection sectors.
We are a preferred global partner to the pharmaceutical, biotech and specialty ingredients markets. We work to prevent illness and promote a healthier world by enabling our customers to deliver innovative medicines that help treat or even cure a wide range of diseases. We also offer a broad range of microbial control solutions, which help to create and maintain a healthy environment.
Founded in 1897 in the Swiss Alps, Lonza today operates in 120 sites and offices in more than 35 countries. With approximately 15,500 full-time employees, we are built from high-performing teams and of individual employees who make a meaningful difference to our own business, as well as the communities in which we operate. The company generated sales of CHF 5.9 billion in 2019 with a CORE EBITDA of CHF 1.6 billion. Find out more at www.lonza.com and follow us on Twitter @LonzaGroup or Facebook @LonzaGroupAG.
All product and company names herein may be trademarks of their registered owners.
FUJIFILM Contact
Christine Jackman
Lonza Contact
Dr. Sanna Fowler
Head of External Communications
Lonza Group Ltd


text:
CHICAGO – Augmenting the lips with grafts of muscle and connective tissue from the neck appears to result in improved appearance for at least two years, according to a report in the March/April issue of Archives of Facial Plastic Surgery, one of the JAMA/Archives journals.
"Since ancient times, women have used plant dyes and colored clays to enhance their lips," the authors write as background information in the article. As an individual ages, the groove on the upper lip flattens, the white lip lengthens and the amount of vermilion (pink tissue) that shows decreases. "These progressive age-related changes lead many patients to seek lip augmentation procedures, often as their main concern in the midst of an aging face and neck."
"The quest for the ideal permanent lip augmentation procedure has been fraught with challenges," they continue, including resorption, asymmetry, reactions, extrusion, an unnatural feel or appearance and the formation of cysts. Anurag Agarwal, M.D., of The Aesthetic Surgery Center, Naples, Fla., and colleagues report on the results of 25 consecutive patients who underwent lip augmentation with segments of their own sternocleidomastoid, a muscle running along the side of the neck, and the connective tissue that overlies it (fascia).
All patients had a minimum follow-up of one year. After an average of two years, the amount of vermilion showing increased by an average of 20 percent to 24 percent for the upper and lower lip. In addition, the average projection of the upper and lower lip increased by an average of 0.9 to 0.99 millimeters. The patients were subjectively pleased with the results, although one requested additional lip augmentation with an injectable gel.
The muscle and fascia can be removed during a concurrent face lift with few complications, the authors note, and are readily incorporated by the lip. There were no deformities in lip contour, limitations in head movement, neck pain or nerve injuries associated with the grafts.
"The postoperative recovery after sternocleidomastoid fascia and muscle grafts to the lips is straightforward," the authors write. "After the first month of lip swelling, the patient should expect that the lips will still be slightly swollen. The senior author's experience has been that approximately 75 percent of the immediate intraoperative lip fullness is maintained at one month post-operatively, while approximately 50 percent of the immediate intraoperative lip fullness is maintained at one year postoperatively." The surgeon must account for this decrease in the size of grafts initially implanted, they note.
"With careful patient selection and surgical technique, sternocleidomastoid muscle and fascia implantation is a valuable tool when treating the aging lip," the authors conclude.
(Arch Facial Plast Surg. 2010;12[2]:97-102. Available at www.jamamedia.org.)

subset: commoncrawl


text:
AMMAN (REUTERS) - President Bashar al-Assad's forces appear to have evacuated most personnel from army and security command headquarters in central Damascus in preparation for a Western military strike, residents and opposition sources said on Wednesday.
US-led air or missile strikes on Syria look all but certain after the United States and European and Middle Eastern allies blamed a suspected poison gas attack that killed hundreds in the city on Aug 21 on President Bashar al-Assad's forces.
Army units stationed near the capital have confiscated several trailer trucks, apparently to transport heavy weaponry to alternative locations, though no significant movement of military hardware has been reported, possibly due to heavy fighting near major highways, one of the sources added.
Among the buildings that have been partially evacuated are the General Staff Command Building on Umayyad Square, the nearby airforce command and the security compounds in the Western Kfar Souseh districts, residents of the area and a Free Syrian Army rebel source said.
The General Staff building, one of the top military headquarters in the country, has been operating with reduced staffing since it was attacked by rebel bombs in September 2012.
But almost no one reported for work at that or the other buildings on Wednesday.
They said trucks have been seen in the last 48 hours at the cordoned off entrance of several buildings, apparently transporting documents and light weapons.
"You can drop a needle in Kfar Souseh and hear it," said a resident who lives near the Palestine branch of Military Intelligence in Kfar Souseh.
Brigadier General Mustafa al-Sheikh, a senior military defector, said from an undisclosed location in Syria that based on Free Syrian Army intelligence gatherings, the general staff command had been moved to an alternative compound in the foothills of the Anti-Lebanon Mountains north of Damascus.
"Various commands are being moved to schools and underground bunkers. But I am not sure it is going to do much good for the regime," Brig Gen Sheikh said.
Another resident who lives at the foothills of Qasioun, the mountain in the middle of the city in which elite praetorian guard units are based, said the boom of artillery, usually heard daily form the 105th battalion of the Republican Guards, had fallen silent on Wednesday. "They have been lots of army trucks descending from Qasioun.
It seems they have evacuated the 105 battalion headquarters," the resident said.
Activists in east Damascus said barracks and housing compounds for the Republican Guards and Fourth Division near the suburbs of Somariya and Mouadamiya had been evacuated and troops and their families had gone into the city.
Abu Ayham, a commander in the Ansar al-Islam rebel brigade in Damascus said the army's general staff and Airforce Intelligence had been evacuated, as well as several mixed-use barracks/housing buildings for the Republican Guards and Fourth Division on the eastern outskirts of the city.
"To all intents and purposes, the army's command and control compounds have been evacuated. Before the threat (of Western strike) they have been taking precautions by working more from lower floors. In the last 48 hours they have been vacated," he said.


text:
People are more productive when they can work anywhere anytime without getting nagging messages like "unable to connect" or "server not found." Just ask Microsoft Outlook users how much they love the offline mode. Application developers agree that enabling their applications to work offline is a customer value-add and an attractive proposition. However, the challenges with building and managing a local cache on top of developing reliable synchronization algorithms are a major concern and a potential risk to product release plans. Truth is: developers' concerns are hardly overstated!
Microsoft Synchronization Services for ADO.NET is a new data synchronization framework that enables developers to build disconnected data applications using familiar concepts. In this document, I will give a quick overview of what the new synchronization framework is all about and how to use it to build occasionally connected applications.
I've been working in Microsoft for over five years focusing on synchronization and replication technologies. I have to admit that I've never been more excited about new synchronization technology than I am with the Synchronization Services framework. The reason is simple: this technology is for developers and not an end-to-end solution that is tailored toward administrators. Anyhow, I thought that it would be a good idea to write an introductory document on this new framework and post it here on The Code Project. After all, you guys are the future users of this API and your feedback is the most important of all.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise) or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, SQL Server, Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.
The Synchronization Services for ADO.NET Beta 2 are available here. Please note that the package contains the SQL CE version 3.5. The documentation is available in a separate package; you can find it here.
ADO.NET introduced a set of disconnected objects that allows you to examine data offline after fetching it from the server. The key to this model is the DataSet object, which encapsulates a host of other disconnected objects like DataTable, DataColumn, etc. Synchronization Services for ADO.NET extends this model by providing a persistent cache on the client. With the data stored on disk on the client machine, the client can examine the data and make modifications while offline and between application restarts. Changes to the data on the client and server are tracked by means of database triggers or through built-in support, as is the case with SQL CE. By using the Sync Services API, incremental changes made on the client and server are exchanged to bring the client cache in sync with the server. The diagram above shows the different components of the sync framework. Below is a brief description of each component:
The sync agent is the synchronization maestro. Typically, it is located at the client side and runs the show in response to client application requests. The agent accepts two sync providers, one for the client database and the other for the server database.
Defines a table that the client wishes to synchronize. This includes the desired direction for the flow of changes, i.e. Snapshot, Downloadonly, Uploadonly or Bidirectional. The SyncTable object allows you to specify your preferred table creation option. When the sync relationship is established in the very first sync, the sync runtime will check the creation option for every table. It then decides how to proceed with the schema creation of the table. If needed, the agent will download the schema definition from the server and apply it on the local database.
The client sync provider abstracts away the underlying data store at the client side. Sync Services ships with ClientSyncProvider for SQL Server CE. SQL CE is a lightweight in-proc database with about a 2MB footprint. You don't have to worry about a thing when it comes to setting up the client. As you will see in the sample application, the tables' schema and all sync-tracking infrastructure are set up for you by the sync runtime.
The server sync provider is where you will write your commands. Sync Services ships with DbServerSyncProvider tailored towards relational stores. It allows you to interact with any database supported by ADO.NET. For each table you wish to synchronize, a SyncAdapter object is needed. SyncAdapter, as described in detail below, is where sync DB commands are located. The provider also exposes two extra commands of its own:
The SyncAdapter is modeled after the DataAdapter, albeit with a different set of database commands for the sync processes:
Although there are more commands on the SyncAdapter compared to DataAdapter, you should not be worried, as not all commands are needed. For example, if you are implementing a download-only scenario, only the three SelectIncremental commands are needed. Moreover, if you just want to get started quickly, the SqlSyncAdapterBuilder can help you generate adapters on the fly at runtime! Some restrictions apply, of course.
Synchronization services can be deployed in different set-ups:
In two-tier set-up, the ClientSyncProvider, SyncAgent and ServerSyncProvider run on the same process or node. In this case, the application will have a direct connection with the back-end database.
In n-tier set-ups, as in the diagram above, the ClientSyncProvider and SyncAgent run in the same process on the client side. The ServerSyncProvider resides on the mid-tier. The sync proxy is a thin wrapper that implements the ServerSyncProvider interface in order to plug seamlessly into the SyncAgent and relay calls to the web service.
Let us put the sync services to work. For this sample, I am developing a line of business applications (LOB) for sales personnel in the field. I want to enable them to enter orders while on the go, using their laptops. At the end of the day, each sales agent connects to the corporate network to synchronize his or her local changes and also receive orders made by other sales agents. That said, I need bidirectional synchronization. For simplicity's sake, I choose to focus on two tables only: order and order_details. The schema for the tables is as follows:
CREATE DATABASE pub
CREATE TABLE pub..orders(
order_id int NOT NULL primary key,
order_date datetime NULL)
CREATE TABLE pub..order_details(
order_id int NOT NULL primary key,
order_details_id int NOT NULL,
product nvarchar(100) NULL,
quantity int NULL)
Take a quick look again at the orders and order_details table definitions. There is no way I can bring incremental changes down to the client. I need to be able to write a simple select statement to enumerate changes that occurred since the last time the client synchronized. To do this, I need to add extra columns to track changes such that I can easily identify new changes that the client has not seen before.
To track inserts and updates, I need the following columns:
-- Add create timestamp column (use bigint since only one timestamp
-- column type is allowed per table)
ALTER TABLE pub..orders add create_timestamp bigint default @@DBTS+1
ALTER TABLE pub..order_details add create_timestamp bigint default @@DBTS+1
-- Add last update timestamp column
ALTER TABLE pub..orders add update_timestamp timestamp
ALTER TABLE pub..order_details add update_timestamp timestamp
-- Create update_originator_id column defaulted to 0 to indicate server change
ALTER TABLE pub..orders add update_originator_id int null default 0
ALTER TABLE pub..order_details add update_originator_id int null default 0
Setting and updating the values of the tracking columns is another matter. The create_timestamp value is only set at insert time and the default constraint should take care of it. The update_timestamp is of type timestamp. This means that SQL server maintains the value for inserts and updates.
The update_originator_id, however, needs a little bit of work. Please note that sync runtime will take care of updating the originator_id column, but if the changes were made outside of sync -- i.e. a user fires up SQL management studio and makes some changes -- then we need to do some fix-up behind the scenes. The desired behavior is to set the value to server_id if a new row is inserted. This is taken care of by the default constraint. If a row is updated, then we need to reset the originator_id back to server_id if and only if the change was not made by sync runtime. To achieve that, I need an update trigger for each table, as shown in the code below:
-- Create Update Triggers
-- Since there will be changes on the server outside of sync application
-- we need triggers to fix up update_originator_id back to 0 which
-- designated for server change
USE pub
CREATE TRIGGER orders_update_trigger on orders FOR UPDATE
-- Note: sync is the only app making changes to update_originator_id,
-- thus we only overwrite the value if it was not set by sync
UPDATE o
SET o.update_originator_id = 0
FROM [orders] o JOIN [inserted] i on o.order_id = i.order_id
WHERE NOT UPDATE(update_originator_id)
CREATE TRIGGER order_details_update_trigger ON order_details FOR UPDATE
-- Note: sync is the only app making changes to update_originator_id,
-- thus we only overwrite the value if it was not set by sync
UPDATE o
SET o.update_originator_id = 0
FROM [order_details] o JOIN [inserted] i on o.order_id = i.order_id
WHERE NOT UPDATE(update_originator_id)
With tracking inserts and updates taken care of, what about deletes? For deletes, I will need a 'tombstone' table to store deleted rows. Tombstone is a term commonly used in synchronization and replication literature. Of course, you can still call it 'deleted table' or anything that works for you. Here are the TSQL statements for creating the tombstone tables:
-- Create tombstone tables to store deletes
CREATE TABLE pub..orders_tombstone(
order_id int NOT NULL primary key,
order_date datetime NULL,
update_originator_id int default 0,
update_timestamp timestamp,
create_timestamp bigint)
CREATE TABLE pub..order_details_tombstone(
order_id int NOT NULL primary key,
order_details_id int NOT NULL,
product nvarchar(100) NULL,
quantity int NULL,
update_originator_id int default 0,
update_timestamp timestamp,
create_timestamp bigint)
While I only need to store the PK to identify the row that was deleted, I prefer to copy the entire row. My reasoning is that later on, when I implement conflict detection and resolution logic (not shown in this sample; see my blog), I would want to represent the deleted row to the end user to resolve the conflict. Showing only the PK is not a great help. Notice that the same tracking columns added to the base tables are created in the tombstone table, too. For the next step -- I bet you figured it already -- we need a delete trigger to copy deletes to the tombstone tables. Here it is:
-- Create Delete Triggers
CREATE TRIGGER orders_delete_trigger ON orders FOR DELETE
INSERT INTO into pub..orders_tombstone (order_id, order_date, _
create_timestamp, update_originator_id)
SELECT order_id, order_date, create_timestamp, 0 FROM DELETED
CREATE TRIGGER order_details_delete_trigger ON order_details FOR DELETE
INSERT INTO pub..order_details_tombstone (order_id, order_details_id,_
product, quantity, create_timestamp, update_originator_id)
SELECT order_id, order_details_id, product, quantity, create_timestamp,_
With that, change tracking is complete and we are set for bidirectional synchronization.
In this example, I am building a two-tier offline application. This means that the client will have a direct connection to the server database to execute queries. The changes made to the back-end tables to track changes conclude the server-side work. Now we switch gears to the client side.
In two-tier set up, the SyncAgent, ClientSyncProvider and ServerSyncProvider will run on the client application. The initialization code below shows the wiring of these three components.
// 1. Create an instance of the SyncAgent
SyncAgent syncAgent = new SyncAgent();
// 2. Prepare server db connection and attach it to the sync agent
DbServerSyncProvider serverSyncProvider = new DbServerSyncProvider();
SqlConnectionStringBuilder builder = new SqlConnectionStringBuilder();
builder["Data Source"] = textServerMachine.Text;
builder["integrated Security"] = true;
builder["Initial Catalog"] = "pub";
SqlConnection serverConnection = new SqlConnection(builder.ConnectionString);
serverSyncProvider.Connection = serverConnection;
SyncAgent.ServerSyncProvider = serverSyncProvider;
// 3. Prepare client db connection and attach it to the sync provider
string connString = "Data Source=" + dbPathTextBox.Text;
if (false == File.Exists(dbPathTextBox.Text))
SqlCeEngine clientEngine = new SqlCeEngine(connString);
SqlCeClientSyncProvider clientSyncProvider =
new SqlCeClientSyncProvider(connString);
syncAgent.ClientSyncProvider = (ClientSyncProvider)clientSyncProvider;
To configure a table for synchronization, a SyncTable object needs to be created and set up with desired properties:
To synchronize changes for both tables in one go, I need to use a common SyncGroup object. This is important if the tables have a PK-FK relationship. Grouping will ensure that an FK change won't be applied before its PK is applied.
// 4. Create SyncTables and SyncGroups
SyncTable tableOrders = new SyncTable("orders");
tableOrders.CreationOption =
tableOrders.SyncDirection = SyncDirection.Bidirectional;
SyncTable tableOrderDetails = new SyncTable("order_details");
tableOrderDetails.CreationOption =
tableOrderDetails.SyncDirection = SyncDirection.Bidirectional;
SyncGroup orderGroup = new SyncGroup("AllChanges");
tableOrders.SyncGroup = orderGroup;
tableOrderDetails.SyncGroup = orderGroup;
In this step, I need to build a SyncAdapter for the orders and order_details tables and attach it to the DbServerSyncProvider instance. Here, I will make use of the tracking columns in each table. While I can go ahead and author each adapter manually, I will use SqlSyncAdapterBuilder to do it instead. All I need to do is feed the builder with the names of the tracking columns, along with the tombstone table name, and it will generate a SyncAdapter for me. The code below shows this process for both tables.
While the SqlSyncAdapterBuilder is a cool tool to get started quickly, it is not intended for production code usage since it makes extra calls to the back-end database to learn about the schema of the tables and data types. This process is repeated in every sync, adding unnecessary overhead.
// 5. Create sync adapter for each sync table and attach it to the server
// provider
SqlSyncAdapterBuilder ordersBuilder = new SqlSyncAdapterBuilder();
ordersBuilder.Connection = serverConnection;
ordersBuilder.SyncDirection = SyncDirection.Bidirectional;
// base table
ordersBuilder.TableName = "orders";
// tombstone table
ordersBuilder.TombstoneTableName = "orders_tombstone";
// tracking\sync columns
ordersBuilder.CreationTrackingColumn = "create_timestamp";
ordersBuilder.UpdateTrackingColumn = "update_timestamp";
ordersBuilder.DeletionTrackingColumn = "update_timestamp";
ordersBuilder.UpdateOriginatorIdColumn = "update_originator_id";
// fix up anchor data type generated by the builder to use Binary
// instead of int64
SyncAdapter ordersSyncAdapter = ordersBuilder.ToSyncAdapter();
"@sync_last_received_anchor"]).DbType = DbType.Binary;
"@sync_new_received_anchor"]).DbType = DbType.Binary;
SqlSyncAdapterBuilder orderDetailsBuilder = new SqlSyncAdapterBuilder();
orderDetailsBuilder.SyncDirection = SyncDirection.Bidirectional;
orderDetailsBuilder.Connection = serverConnection;
// base table
orderDetailsBuilder.TableName = "order_details";
// tombstone table
orderDetailsBuilder.TombstoneTableName = "order_details_tombstone";
// tracking\sync columns
orderDetailsBuilder.CreationTrackingColumn = "create_timestamp";
orderDetailsBuilder.UpdateTrackingColumn = "update_timestamp";
orderDetailsBuilder.DeletionTrackingColumn = "update_timestamp";
orderDetailsBuilder.UpdateOriginatorIdColumn = "update_originator_id";
// fix up anchor data type generated by the builder to use Binary
// instead of int64
SyncAdapter orderDetailsSyncAdapter = orderDetailsBuilder.ToSyncAdapter();
"@sync_last_received_anchor"]).DbType = DbType.Binary;
"@sync_new_received_anchor"]).DbType = DbType.Binary;
As I mentioned before, the DbServerSyncProvider has two more commands. Let's see how to configure them:
Select @@DBTS
// 6. set up provider wide commands
// select new anchor command
SqlCommand anchorCmd = new SqlCommand();
anchorCmd.CommandType = CommandType.Text;
anchorCmd.CommandText =
"Select @" + SyncSession.SyncNewReceivedAnchor + " = @@DBTS";
anchorCmd.Parameters.Add("@" + SyncSession.SyncNewReceivedAnchor,
SqlDbType.Timestamp).Direction = ParameterDirection.Output;
serverSyncProvider.SelectNewAnchorCommand = anchorCmd;
// client ID command (give the client id of 1)
// in remote server scenario (middle tear), this command will reference a
// local client table for the ID
SqlCommand clientIdCmd = new SqlCommand();
clientIdCmd.CommandType = CommandType.Text;
clientIdCmd.CommandText = "SELECT @" + SyncSession.SyncOriginatorId + " = 1";
clientIdCmd.Parameters.Add("@" + SyncSession.SyncOriginatorId,
SqlDbType.Int).Direction = ParameterDirection.Output;
serverSyncProvider.SelectClientIdCommand = clientIdCmd;
The client ID of 1 works fine if there is only one client. This is just to get you started quickly. But what should you do to handle multiple clients? In this case, you need a unique new number for every client. To do this without writing a lot of code, you can use yet another built-in session parameter called sync_client_id. This parameter is of the type GUID that is generated by the client when it is initialized in the very first sync. While using GUID as the update_originator_id is possible, it is not a very attractive idea as it increases the size of the table unnecessarily. All I really need is an integer and that's why I chose that from the beginning. The best solution is to implement a simple mapping table {identity, client_guid} and maintain it on the server. To do that, the SelectClientIdCommand would implement the following semantics:
You get the idea. Luckily for us, the framework provides a simple way to avoid doing that while in experimental phase. This is done by passing the hash value of the GUID, which is of type integer. Of course, there is a possibility of a hash collision but again, this is for testing purposes only. The code would look like the following:
SqlCommand clientIdCmd = new SqlCommand();
clientIdCmd.CommandType = CommandType.Text;
clientIdCmd.CommandText =
"SELECT @" + SyncSession.SyncOriginatorId + " = @sync_client_id_hash";
clientIdCmd.Parameters.Add("@sync_client_id_hash", SqlType.Int);
clientIdCmd.Parameters.Add("@" + SyncSession.SyncOriginatorId,
SqlDbType.Int).Direction = ParameterDirection.Output;
serverSyncProvider.SelectClientIdCommand = clientIdCmd;
Now we are set to kick off synchronization. Before that, I'd like to subscribe to SyncProgressEvent on both providers so that I can show a progress dialog while synchronization is underway.
// 7. Kickoff Sync
clientSyncProvider.SyncProgress += new
serverSyncProvider.SyncProgress += new
SyncStatistics syncStats = syncAgent.Synchronize();
The interest in offline experience is growing rapidly, fueled by a new breed of rich internet applications. The vision of software as a service where the application has a web component and a desktop component stresses the need for synchronization as the glue that ties these components together. However, synchronization technologies have not become mainstream yet. Few developers have the know-how to build sync-enabled applications. With Microsoft Synchronization Services for ADO.NET, developers have a starting point to get into sync algorithms and learn how to extend their data applications with offline components.
In this document, I shared with you the first demo application of a series of demos that I prepared to showcase the new API. The rest of the demos are posted on my blog and website. Each demo builds on the previous one and shows a new feature of the API. Here is a quick overview of the demo series:
I'd appreciate if people can post issues, requests, questions, etc. in the public forum. The forum is monitored by many people in the sync team and is thus a more effective way of communication. I also hope that I was able to introduce the new framework to you through this article. The only way I will know if you like it is by rating it. Please vote when you can. You can also contact me through my blog.
This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
General News Suggestion Question Bug Answer Joke Praise Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.


text:
Below you find a quick list of destinations within about 15 miles of Thompson Park Off-leash Dog Area (Monmouth County). You can browse by activity type, general category (like a park) or rentals/outfitters. If you are looking for information about Thompson Park Off-leash Dog Area (Monmouth County), and not about destinations nearby, please click the "Overview" tab above.
1 Search Results
Garden State Velodrome, at Wall Raceway 11.06 miles
The 400m Garden State Velodrome is part of the Wall stadium speedway. The facility, is a member of American Track R...
LocationGarden State Velodrome, at Wall Raceway
1803 Highway 34 South,
Wall Township, NJ 07719
AttractionsBMX / Bike trackRacing / Race Track
Sports PlusBMX / Bike track


text:
This entry was posted on Wednesday, May 5th, 2021 at 8:43 am and is filed under Stops. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
« Listen to the Cupcake Brake THEME SONG by Sugarhill Productions!


text:
The Day In Pot, And There's A Lot – November 21, 2012
Humboldt County District Attorney's Office Press Release
FIELDBROOK – On Wednesday, Nov. 21, investigators from the Humboldt County District Attorney's Office executed a search warrant at 26 Old Quarry Lane, Fieldbrook. During the course of their investigation, Investigators had learned that the property was often patrolled by Belgian Malinois guard dogs. To provide additional assistance and scene security, the Humboldt County Sheriff's Office assigned two deputies in marked patrol units to assist in securing the scene.
While conducting the search, Investigators located a complex indoor marijuana cultivation, drying, and processing area in a converted two-story barn structure. (104) 8" marijuana starter plants were found growing, but the bulk of the marijuana had been harvested and was in the process of being dried.
In total, investigators seized approximately 34.5 pounds of drying marijuana, an additional 14 pounds of marijuana that was packaged for the purposes of sales, a small quantity of MDMA ("Ecstasy), packaging materials, scales, and $10,375 in U.S. currency which is believed to be the proceeds of illegal drug sales.
Michael Greenwood (age 36) and his wife Vera Snow-Greenwood (age 27) were arrested for H&S11358 – Cultivation of Marijuana, H&S11359 – Possession of Marijuana for Purposes of Sales, H&S11366.5 – Maintaining a Residence for the Purpose of Marijuana Cultivation, H&S11377(a) – Possession of a Controlled Substance, and PC273(a) – Child Endangerment.
Four young children who were located inside the residence were released to family members.
GARBERVILLE – On Wednesday, Nov. 21, 2012 a Garberville Area CHP Officer observed a green 2004 Jeep Laredo traveling southbound on US-101 at a high rate of speed through Richardson Grove, resulting in an enforcement stop north of the Mendocino County line. The Jeep's driver was identified by his California Drivers License as Luis Alonso Nolasco (DOB: 12/21/1972) from Paramount, California.
While speaking with Mr. Nolasco, the officer recognized the strong odor of marijuana emitting from inside the Jeep. Mr. Nolasco also related that there was marijuana inside the vehicle. During a subsequent investigation, approximately 111 pounds of processed and packaged marijuana was located inside the Jeep.
The marijuana was processed and packaged in clear plastic bags, each weighing nearly a pound.
Mr. Nolasco was placed under arrest on suspicion of marijuana cultivation, possession and transportation for sales. The Humboldt County Drug Task Force (HCDTF) responded to the scene and assisted Garberville Area CHP with this incident.


text: Invisible Kid last edited by pikahyper on 02/12/20 06:19PM View full history This page is for the original Invisible Kid, Lyle Norg.For the current Invisible Kid, see: Jacques FoccartOriginLyle NorgLyle Norg was a a genius and prodigy in biochemistry. He created a serum that allowed him to turn invisible, and earned a place in the Legion of Super-Heroes as one of its earliest members shortly after Colossal Boy and Chameleon Boy. A dedicated member, Lyle often engaged in regular exercise and combat training to make his contributions to the Legion greater. Though he often served covertly in the background, Lyle's peers recognized his accomplishments and he was eventually elected the Legion's fourth leader in the team's fifth term.CreationLyle Norg was created by Jerry Siegel and Jim Mooney. Lyle was the first election where the readers were able to vote for Legion leader and Lyle's success is largely attributed to the readership wanting to see him get more to do. Earth-247 Lyle was later revealed as gay, though this was only hinted at during his publication.Character EvolutionOriginal Continuity: New EarthInvisible Kid (Pre-Crisis)Lyle was instrumental in helping the Legion win back Earth from its possession by Universo. Following his stint as leader, Lyle began to aid Legion cadet Chemical King in the use of his powers and the two became fast friends. After several years of service, Lyle began to be haunted by a ephemeral girl named Myla. Despite her intangibility, the two got along well and Lyle became romantically interested in her.Reboot: Earth-247Invisible Kid (Earth-247)The rebooted Lyle Norg was born on Earth-247 to scientist parents who often spent long periods of time away from home. As a result, young Lyle was predominantly raised by the Foccart family. A child prodigy, Lyle became interested in chemistry at an early age thanks to the Foccarts. Initially, he only created and patented things like new flavors of ice cream, but soon became more complex with his creations. His greatest invention was a serum that bent light around his body and clothing, rendering him invisible at will. EarthGov became interested in Lyle's discovery and enlisted him to do some investigative work for them. He was joined by the powerless Jacques Foccart, whom Lyle considered a brother, and the young woman who would one day become the villainous Charma. Lyle's knowledge of the Durlan language and close friendship with Chameleon suggests that he spent time on Durla during these days. On his last mission, Lyle was tricked into stealing his own formula. Jacques consumed it, but unlike Lyle he appeared to simply fade from existence. Disgusted, Lyle quit EarthGov and was instead drafted by Earth into the Legion of Super-Heroes.Threeboot: Earth-PrimeInvisible Kid (Earth-Prime)Lyle was a child prodigy in this reality who was asked by his father and the government to create an invisibility serum. Upon learning that his father had planned to give it away for military use, Lyle decided to inject himself with the only sample so that it could never fall upon abusive hands. He lied about injecting himself, claiming instead the serum never worked. Lyle then contacted his colleague, Brainiac 5 of the Legion of Super-Heroes, for help in escaping from his parents who had registered him on public service. Lyle and Brainy had previously collaborated on the Legion flight rings. Brainy sponsored Lyle for Legion membership and he was accepted as Invisible Kid. At odds with his parents for running away, especially his military father, Lyle would later reconcile with the Norgs.Retroboot: New EarthInvisible Kid (New Earth)The events of Infinite Crisis brought together the Legions of all three continuities. Afterward, the current Legion of Super-Heroes returned to being a close approximation of the original Pre-Crisis team, once again set on New Earth. Thus, Lyle Norg was deceased again. A statue continued to stand in his honor in the Legion's memorial room. Invisible Kid II, also back in continuity, served still on the Legion in Lyle's honor.Major Story ArcsOriginal Continuity: New EarthThe Death of Lyle NorgThe death of Invisible KidWhen the villain Validus attacked Legion Headquarters to steal a device, Lyle was on invisible guard. He destroyed the device to prevent it from falling into enemy hands, but in the process was caught and crushed by Validus, killing Lyle. Myla then appeared to the Legion, revealing herself a ghost and promising to take care of Lyle in the afterlife. He was mourned by the Legion, especially Chemical King and Brainiac 5. Following Lyle's death, his serum was protected by Brainy and was later used in a time of crisis to give powers to Jacques Foccart, who would go on to become Lyle's successor as Invisible Kid.Reboot: Earth-247Legion Espionage SquadCharma and his brother JacquesLyle was a stalwart member of the team and founder of the Legion Espionage Squad to do undercover work. He was instrumental in helping Cosmic Boy reveal that President Jeanne Chu was the mastermind behind the Braal-Titan War and helped Chameleon adapt to life on Earth. He even aided Cham in giving secret admirer gifts to Spark, who mistook them as being from Invisible Kid. When half the Legion was trapped in the 20th century, Lyle remained in the 30th and was elected leader by the membership. Though he didn't want the job, Lyle proved adept at handling it. Months later, when the Legion was reunited, Lyle stepped down from leadership for private reasons and gave the job to Saturn Girl. Lyle was later captured by his old teammate Charma, seeking revenge on him. Lyle was freed by an unknown force, which he suspected may have been his lost "brother," Jacques.The BlightThe BlightWhen the Blight invaded Earth, Lyle was deemed a threat and had a choke-weed used on him that took him underground and used him as a living battery. He would have died if not for the Legion's timely defeat of the Blight. The team was later disbanded and Lyle began covertly working with R.J. Brande to assemble Legion World. Lyle helped found the reformed team and served with them until they were lost in the timestream and Earth-247 was destroyed. He and his teammates are now part of the new Wanderers of the multiverse.Threeboot: Earth-PrimeLeader of The Legion Espionage SquadGiselle (Gazaelle)Lyle and the Legion helped the Wanderers fight the Dominators when the aliens invaded Earth. During the battle, Lyle's flight ring blew up, and he lost his arm. He received an arm graft for a short period of time before a proper arm could be regrown for him. He developed feelings for time-lost member Supergirl, who didn't reciprocate and ultimately left the team. On a mission to Triton, Lyle developed feelings for a local girl named Giselle who had been ridiculed by her people, but was afraid to show himself to her. To investigate matters that didn't fall under the Legion's proper jurisdiction, Lyle formed the top-secret Legion Espionage Squad and served as its leader. Eventually, Giselle joined the Legion as Gazelle. Lyle, still hiding from his crush, used virtual reality to make himself appear older and buffer than he truly was. Gazelle was fond of this form, but when Lyle's ruse was uncovered she didn't seem to mind the real Lyle either.Powers and AbilitiesInvisibilityInvisible Kid developed and consumed a serum that allowed him to turn any or all parts of his body invisible at will. In the post-boot reality, he could make others invisible though it took extreme concentration.EquipmentLegion Flight RingAs a member of the Legion of Super-Heroes, Invisible Kid possesses a Legion Flight Ring. The ring gives its wearer the ability to fly, the speed and range of which is determined by the wearer's willpower. It also acts as a long-range communicator (enabling constant vocal contact with other Legionnaires, even across vast distances of space), a signal device, and a navigational compass, all powered by a micro-computer built inside the ring.Other VersionsFive Years Later: Batch SW6Invisible Kid (Batch SW6)At least a decade later, following the Five Year Later of the Magic Wars. The Dominators located time-displaced copies of the Legion of Super-Heroes from their younger days, including Invisible Kid. They were dubbed Batch SW6. The team in fact only had memories up until Invisible Kid's time as leader, so the young Lyle became the defacto leader again and aided them in their survival on a dystopian Earth. These young Legionnaires eventually met up with their adult counterparts and Lyle was surprised to learn that he had died. He later met his parents, 17 years older than he remembered and who were ecstatic to see their son alive again. These young heroes went on to become the Legionnaires of New Earth, where Lyle protested another stint as leader and helped nominate Cosmic Boy. Lyle served as a Legionnaire until Zero Hour, where he and several other scientists discovered that the timestream was collapsing on their reality. Lyle was one of many causalities before this continuity was wiped from existence, having faded away in-between issues.Other Media Font-sizeParagraphHeader 4Header 3Header 2 Quote Link Img Table TweetClean sizeSMLpositionLCRUDchangeCreditDeletesizeSMpositionLRUDchangetitle 1title 2captiondelete×Edit Image TitleTitle: CancelUpdate×Embed ImageWhat size image should we insert? (This will not affect the original upload) Small Medium How do you want the image positioned around text? Float Left Float Right CancelInsertGo to LinkUnlinkChange× Link to Comic Vine Content AllWiki Arcs Characters Companies Concepts Issues Locations Movies People Teams Things Volumes Series EpisodesEditorial Videos Articles Reviews FeaturesCommunity Users You can search for any Comic Vine content. CancelCreate Link×Link to a pageAllWiki Arcs Characters Companies Concepts Issues Locations Movies People Teams Things Volumes Series EpisodesEditorial Videos Articles Reviews FeaturesCommunity Users You can search for any Comic Vine content. Disable this feature for this sessionpositionUDchangeDeletepositionUDchangeDeletepositionUDchangeDeleteInsert Row UpInsert Row DownInsert Column LeftInsert Column RightDelete RowDelete ColumnbordersonheaderonpositionUDtablemax-widthdelete×Insert TableRows: Columns: CancelInsertpositionLCRUDchangeDelete×Embed tweetEnter the URL for the tweet you want to embed.CancelInsert


text:
hwloc is organized in components that are responsible for discovering objects. Depending on the topology configuration, some components will be used, some will be ignored. The usual default is to enable the native operating system component, (e.g. linux or solaris) and the libpci additional component. If available, an architecture-specific component (such as x86) may also improve the topology detection.
If a XML topology is loaded, the xml discovery component will be used instead of all other components. It internally uses a specific class of components for the actual XML import/export routines (xml_libxml and xml_nolibxml) but these will not be discussed here (see libxml2 and minimalistic XML backends).
The hwloc core contains a list of components sorted by priority. Each one is enabled as long as it does not conflict with the previously enabled ones. This includes native operating system components, architecture-specific ones, and if available, I/O components such as libpci.
Usually the native operating system component (when it exists, e.g. linux or aix) is enabled first. Then hwloc looks for an architecture specific component (e.g. x86). Finally these also exist a basic component (no_os) that just tries to discover the number of PUs in the system.
Each component discovers as much topology information as possible. Most of them, including most native OS components, do nothing unless the topology is still empty. Some others, such as x86 and libpci, can complete and annotate what other backends still earlier.
Default priorities ensure that clever components are invoked first. Native operating system components have higher priorities, and are therefore invoked first, because they likely offer very detailed topology information. If needed, it will be later extended by architecture-specific information (e.g. from the x86 component).
If any configuration function such as hwloc_topology_set_xml() is used before loading the topology, the corresponding component is enabled first. Then, as usual, hwloc enables any other component (based on priorities) that does not conflict.
Certain components that manage a virtual topology, for instance XML topology import, synthetic topology description, or custom building, conflict with all other components. Therefore, one of them may only be loaded (e.g. with hwloc_topology_set_xml()) if no other component is enabled.
The environment variable HWLOC_COMPONENTS_VERBOSE may be set to get verbose messages about component registration (including their priority) and enabling.
Aside from topology configuration function such as hwloc_topology_set_custom(), the default priority order may be changed through the HWLOC_COMPONENTS environment variable (component names must be separated by commas).
Specifying x86 in this variable will cause the x86 component to take precedence over any other component, including the native operating system component. It is therefore loaded first, before hwloc tries to load all remaining non-conflicting components. In this case, x86 would take care of discovering everything it supports, instead of only completing what the native OS information. This may be useful if the native component is buggy on some platforms.
It is possible to prevent all remaining components from being loaded by placing stop in the environment variable. Only the components listed before this keyword will be enabled.
Certain component names (xml and synthetic) accept an argument (e.g. xml=file.xml). These arguments behave exactly as if the corresponding string had been passed to hwloc_topology_set_xml() or hwloc_topology_set_synthetic().
Components may optionally be built as plugins so that the hwloc core library does not directly depend on their dependencies (for instance the libpci library). Plugin support may be enabled with the –enable-plugins configure option. All components buildable as plugins will then be built as plugins. The configure option may be given a comma-separated list of component names to specify the exact list of components to build as plugins.
Plugins are built as independent dynamic libraries that are installed in $libdir/hwloc. All plugins found in this directory are loaded during topology_init(). A specific list of directories (colon-separated) to scan may be specified in the HWLOC_PLUGINS_PATH environment variable.
Plugin filenames must start with hwloc_. For instance the libpci plugin is usually built as hwloc_libpci.so.
Note that loading a plugin just means that the corresponding component is registered to the hwloc core. Components are then only enabled if the topology configuration requests it, as explained in the previous sections.
Each new discovery component requires a new hwloc_component structure to be exported to the hwloc core with name hwloc_<name>_component. The configure script should then be modified to add <name> to the hwloc_components variable so that the component is actually available at runtime.
If the new component may be built as a plugin, the configure script should also define hwloc_<name>_component_maybeplugin=1. If the configure scripts decides to enable the component as a plugin, the variable hwloc_<name>_component will be set to plugin. The build system may then use this variable to actually change the way the component is built.
The component structure contains a data field that points to an hwloc_disc_component which defines an instantiate callback. This function is invoked when this component is actually used by a topology. It creates a backend structure that usually contains a discover and/or notify_new_object callback taking care of the actual topology discovery.
All components distributed within hwloc are listed below. The list of actually available components may be listed at running with the HWLOC_COMPONENTS_VERBOSE environment variable (see Environment Variables).