How to let users decide between transactions

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












I am building an API that will send out signed transactions to users and allow them to submit the transactions themselves.



I am attempting to send a user three different transactions however I would like the user to select between these options and select only one.



Question is; once the user submits one of these transactions, how do I prevent the others being sent?



I was attempting to use sequence numbers to prevent this but cannot figure out how to assign the same sequence id to all transactions on the javascript SDK so that only one is accepted.



Is there a better way to do this and if not how can I set the sequence number with the JS-sdk?




stellar-sdk




share|improve this question




















  • Thank you all; these solutions are correct and I was able to manually set the sequence number in the account object before each transaction to ensure it was the same.
    – Momentus Mitch
    Aug 20 at 16:38














up vote
2
down vote

favorite












I am building an API that will send out signed transactions to users and allow them to submit the transactions themselves.



I am attempting to send a user three different transactions however I would like the user to select between these options and select only one.



Question is; once the user submits one of these transactions, how do I prevent the others being sent?



I was attempting to use sequence numbers to prevent this but cannot figure out how to assign the same sequence id to all transactions on the javascript SDK so that only one is accepted.



Is there a better way to do this and if not how can I set the sequence number with the JS-sdk?




stellar-sdk




share|improve this question




















  • Thank you all; these solutions are correct and I was able to manually set the sequence number in the account object before each transaction to ensure it was the same.
    – Momentus Mitch
    Aug 20 at 16:38












up vote
2
down vote

favorite









up vote
2
down vote

favorite











I am building an API that will send out signed transactions to users and allow them to submit the transactions themselves.



I am attempting to send a user three different transactions however I would like the user to select between these options and select only one.



Question is; once the user submits one of these transactions, how do I prevent the others being sent?



I was attempting to use sequence numbers to prevent this but cannot figure out how to assign the same sequence id to all transactions on the javascript SDK so that only one is accepted.



Is there a better way to do this and if not how can I set the sequence number with the JS-sdk?




stellar-sdk




share|improve this question












I am building an API that will send out signed transactions to users and allow them to submit the transactions themselves.



I am attempting to send a user three different transactions however I would like the user to select between these options and select only one.



Question is; once the user submits one of these transactions, how do I prevent the others being sent?



I was attempting to use sequence numbers to prevent this but cannot figure out how to assign the same sequence id to all transactions on the javascript SDK so that only one is accepted.



Is there a better way to do this and if not how can I set the sequence number with the JS-sdk?





stellar-sdk





share|improve this question











share|improve this question




share|improve this question










asked Aug 20 at 1:07









Momentus Mitch

1134




1134











  • Thank you all; these solutions are correct and I was able to manually set the sequence number in the account object before each transaction to ensure it was the same.
    – Momentus Mitch
    Aug 20 at 16:38
















  • Thank you all; these solutions are correct and I was able to manually set the sequence number in the account object before each transaction to ensure it was the same.
    – Momentus Mitch
    Aug 20 at 16:38















Thank you all; these solutions are correct and I was able to manually set the sequence number in the account object before each transaction to ensure it was the same.
– Momentus Mitch
Aug 20 at 16:38




Thank you all; these solutions are correct and I was able to manually set the sequence number in the account object before each transaction to ensure it was the same.
– Momentus Mitch
Aug 20 at 16:38










3 Answers
3






active

oldest

votes

















up vote
6
down vote



accepted










The same sequence number is the solution for this case. I also had the similar issue setting up same sequence number for multiple transactions, here's a sample js sdk code I used to set same sequence number,



// This method is not recommended but seems to be only working options
// I could find at the time.

// load account, which will have initial sequence number
var account = await server.loadAccount(public);

const transaction1 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// the sequence number has increased, I had tried many methods for setting
// the same sequence number, but nothing seems to work,

// Solution I used, load the account again

account = await server.loadAccount(public);

const transaction2 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// This transaction has same sequence number





share|improve this answer
















  • 1




    Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
    – Paul
    Aug 20 at 13:23


















up vote
1
down vote













Having the same sequence number for each transaction is the perfect solution. (Well almost perfect. This will get you at most one, rather than exactly one).



In regard to managing the sequence number, the docs state:




There are two ways to ensure correct sequence numbers:



  1. Read the source account’s sequence number before submitting a transaction

  2. Manage the sequence number locally



I read this to mean that the JS library will not automatically update the sequence number each time a transaction is built. You should be OK to fetch the sequence number once (from Horizon or your app's local store if you are keeping track) and build 3 transactions with that sequence number.






share|improve this answer
















  • 1




    The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
    – Johan Stén
    Aug 20 at 2:17











  • The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
    – Momentus Mitch
    Aug 20 at 16:39

















up vote
0
down vote













TransactionBuilder takes an Account object as its first parameter,
an Account consists of a public key, and a sequence number.



You can do loadAccount once, to get the current sequence number, and then simply re-use it (the sequence number) for the next transactions.



const account = await server.loadAccount(accoundId);
const sequenceNumber = account.sequenceNumber();


then every time you want to create a transaction:



const account = new StellarSdk.Account(accountId, sequenceNumber); 
const builder = new StellarSdk.TransactionBuilder(account);





share|improve this answer


















  • 1




    Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
    – Paul
    Aug 20 at 13:20






  • 1




    Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
    – Johan Stén
    Aug 20 at 15:06











  • We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
    – Momentus Mitch
    Aug 20 at 16:40










  • What you do is what Paul and I have been saying all along..
    – Johan Stén
    Aug 21 at 4:43











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "686"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstellar.stackexchange.com%2fquestions%2f1482%2fhow-to-let-users-decide-between-transactions%23new-answer', 'question_page');

);

Post as a guest

















3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
6
down vote



accepted










The same sequence number is the solution for this case. I also had the similar issue setting up same sequence number for multiple transactions, here's a sample js sdk code I used to set same sequence number,



// This method is not recommended but seems to be only working options
// I could find at the time.

// load account, which will have initial sequence number
var account = await server.loadAccount(public);

const transaction1 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// the sequence number has increased, I had tried many methods for setting
// the same sequence number, but nothing seems to work,

// Solution I used, load the account again

account = await server.loadAccount(public);

const transaction2 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// This transaction has same sequence number





share|improve this answer
















  • 1




    Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
    – Paul
    Aug 20 at 13:23















up vote
6
down vote



accepted










The same sequence number is the solution for this case. I also had the similar issue setting up same sequence number for multiple transactions, here's a sample js sdk code I used to set same sequence number,



// This method is not recommended but seems to be only working options
// I could find at the time.

// load account, which will have initial sequence number
var account = await server.loadAccount(public);

const transaction1 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// the sequence number has increased, I had tried many methods for setting
// the same sequence number, but nothing seems to work,

// Solution I used, load the account again

account = await server.loadAccount(public);

const transaction2 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// This transaction has same sequence number





share|improve this answer
















  • 1




    Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
    – Paul
    Aug 20 at 13:23













up vote
6
down vote



accepted







up vote
6
down vote



accepted






The same sequence number is the solution for this case. I also had the similar issue setting up same sequence number for multiple transactions, here's a sample js sdk code I used to set same sequence number,



// This method is not recommended but seems to be only working options
// I could find at the time.

// load account, which will have initial sequence number
var account = await server.loadAccount(public);

const transaction1 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// the sequence number has increased, I had tried many methods for setting
// the same sequence number, but nothing seems to work,

// Solution I used, load the account again

account = await server.loadAccount(public);

const transaction2 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// This transaction has same sequence number





share|improve this answer












The same sequence number is the solution for this case. I also had the similar issue setting up same sequence number for multiple transactions, here's a sample js sdk code I used to set same sequence number,



// This method is not recommended but seems to be only working options
// I could find at the time.

// load account, which will have initial sequence number
var account = await server.loadAccount(public);

const transaction1 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// the sequence number has increased, I had tried many methods for setting
// the same sequence number, but nothing seems to work,

// Solution I used, load the account again

account = await server.loadAccount(public);

const transaction2 = new StellarSdk.TransactionBuilder(account)
 .addOperation(...).build();

// This transaction has same sequence number






share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 20 at 6:46









Ashish Prajapati

1847




1847







  • 1




    Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
    – Paul
    Aug 20 at 13:23













  • 1




    Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
    – Paul
    Aug 20 at 13:23








1




1




Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
– Paul
Aug 20 at 13:23





Looks like you should be able to rebuild the account with the current sequence number using new Account(publicKey, sequenceNumber)
– Paul
Aug 20 at 13:23











up vote
1
down vote













Having the same sequence number for each transaction is the perfect solution. (Well almost perfect. This will get you at most one, rather than exactly one).



In regard to managing the sequence number, the docs state:




There are two ways to ensure correct sequence numbers:



  1. Read the source account’s sequence number before submitting a transaction

  2. Manage the sequence number locally



I read this to mean that the JS library will not automatically update the sequence number each time a transaction is built. You should be OK to fetch the sequence number once (from Horizon or your app's local store if you are keeping track) and build 3 transactions with that sequence number.






share|improve this answer
















  • 1




    The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
    – Johan Stén
    Aug 20 at 2:17











  • The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
    – Momentus Mitch
    Aug 20 at 16:39














up vote
1
down vote













Having the same sequence number for each transaction is the perfect solution. (Well almost perfect. This will get you at most one, rather than exactly one).



In regard to managing the sequence number, the docs state:




There are two ways to ensure correct sequence numbers:



  1. Read the source account’s sequence number before submitting a transaction

  2. Manage the sequence number locally



I read this to mean that the JS library will not automatically update the sequence number each time a transaction is built. You should be OK to fetch the sequence number once (from Horizon or your app's local store if you are keeping track) and build 3 transactions with that sequence number.






share|improve this answer
















  • 1




    The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
    – Johan Stén
    Aug 20 at 2:17











  • The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
    – Momentus Mitch
    Aug 20 at 16:39












up vote
1
down vote










up vote
1
down vote









Having the same sequence number for each transaction is the perfect solution. (Well almost perfect. This will get you at most one, rather than exactly one).



In regard to managing the sequence number, the docs state:




There are two ways to ensure correct sequence numbers:



  1. Read the source account’s sequence number before submitting a transaction

  2. Manage the sequence number locally



I read this to mean that the JS library will not automatically update the sequence number each time a transaction is built. You should be OK to fetch the sequence number once (from Horizon or your app's local store if you are keeping track) and build 3 transactions with that sequence number.






share|improve this answer












Having the same sequence number for each transaction is the perfect solution. (Well almost perfect. This will get you at most one, rather than exactly one).



In regard to managing the sequence number, the docs state:




There are two ways to ensure correct sequence numbers:



  1. Read the source account’s sequence number before submitting a transaction

  2. Manage the sequence number locally



I read this to mean that the JS library will not automatically update the sequence number each time a transaction is built. You should be OK to fetch the sequence number once (from Horizon or your app's local store if you are keeping track) and build 3 transactions with that sequence number.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 20 at 2:15









Synesso♦

1,871222




1,871222







  • 1




    The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
    – Johan Stén
    Aug 20 at 2:17











  • The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
    – Momentus Mitch
    Aug 20 at 16:39












  • 1




    The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
    – Johan Stén
    Aug 20 at 2:17











  • The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
    – Momentus Mitch
    Aug 20 at 16:39







1




1




The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
– Johan Stén
Aug 20 at 2:17





The JS library actually does update the sequence number each time a transaction is built, but it's based on the parameters you give to it. Send in the same (account id, sequence number) tuple, and you're good to go.
– Johan Stén
Aug 20 at 2:17













The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
– Momentus Mitch
Aug 20 at 16:39




The sequence number is locally updated on the account object per 'build()' call. However I was able to manually decrement or set the sequence number in the account object to be the same. Thanks!
– Momentus Mitch
Aug 20 at 16:39










up vote
0
down vote













TransactionBuilder takes an Account object as its first parameter,
an Account consists of a public key, and a sequence number.



You can do loadAccount once, to get the current sequence number, and then simply re-use it (the sequence number) for the next transactions.



const account = await server.loadAccount(accoundId);
const sequenceNumber = account.sequenceNumber();


then every time you want to create a transaction:



const account = new StellarSdk.Account(accountId, sequenceNumber); 
const builder = new StellarSdk.TransactionBuilder(account);





share|improve this answer


















  • 1




    Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
    – Paul
    Aug 20 at 13:20






  • 1




    Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
    – Johan Stén
    Aug 20 at 15:06











  • We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
    – Momentus Mitch
    Aug 20 at 16:40










  • What you do is what Paul and I have been saying all along..
    – Johan Stén
    Aug 21 at 4:43















up vote
0
down vote













TransactionBuilder takes an Account object as its first parameter,
an Account consists of a public key, and a sequence number.



You can do loadAccount once, to get the current sequence number, and then simply re-use it (the sequence number) for the next transactions.



const account = await server.loadAccount(accoundId);
const sequenceNumber = account.sequenceNumber();


then every time you want to create a transaction:



const account = new StellarSdk.Account(accountId, sequenceNumber); 
const builder = new StellarSdk.TransactionBuilder(account);





share|improve this answer


















  • 1




    Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
    – Paul
    Aug 20 at 13:20






  • 1




    Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
    – Johan Stén
    Aug 20 at 15:06











  • We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
    – Momentus Mitch
    Aug 20 at 16:40










  • What you do is what Paul and I have been saying all along..
    – Johan Stén
    Aug 21 at 4:43













up vote
0
down vote










up vote
0
down vote









TransactionBuilder takes an Account object as its first parameter,
an Account consists of a public key, and a sequence number.



You can do loadAccount once, to get the current sequence number, and then simply re-use it (the sequence number) for the next transactions.



const account = await server.loadAccount(accoundId);
const sequenceNumber = account.sequenceNumber();


then every time you want to create a transaction:



const account = new StellarSdk.Account(accountId, sequenceNumber); 
const builder = new StellarSdk.TransactionBuilder(account);





share|improve this answer














TransactionBuilder takes an Account object as its first parameter,
an Account consists of a public key, and a sequence number.



You can do loadAccount once, to get the current sequence number, and then simply re-use it (the sequence number) for the next transactions.



const account = await server.loadAccount(accoundId);
const sequenceNumber = account.sequenceNumber();


then every time you want to create a transaction:



const account = new StellarSdk.Account(accountId, sequenceNumber); 
const builder = new StellarSdk.TransactionBuilder(account);






share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 21 at 4:47

























answered Aug 20 at 2:16









Johan Stén

7709




7709







  • 1




    Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
    – Paul
    Aug 20 at 13:20






  • 1




    Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
    – Johan Stén
    Aug 20 at 15:06











  • We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
    – Momentus Mitch
    Aug 20 at 16:40










  • What you do is what Paul and I have been saying all along..
    – Johan Stén
    Aug 21 at 4:43













  • 1




    Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
    – Paul
    Aug 20 at 13:20






  • 1




    Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
    – Johan Stén
    Aug 20 at 15:06











  • We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
    – Momentus Mitch
    Aug 20 at 16:40










  • What you do is what Paul and I have been saying all along..
    – Johan Stén
    Aug 21 at 4:43








1




1




Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
– Paul
Aug 20 at 13:20




Yes, but you have to be careful to re-use the sequence number (by resetting it manually), not just use the same account over and over again. The sequence number of the source account is bumped by the various SDKs when the transaction is built, not when it is submitted.
– Paul
Aug 20 at 13:20




1




1




Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
– Johan Stén
Aug 20 at 15:06





Definitely, you have to get the sequence number out of the Account, and create a new Account for each TransactionBuilder you create. Your comment is what I commented to Jem already :)
– Johan Stén
Aug 20 at 15:06













We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
– Momentus Mitch
Aug 20 at 16:40




We can use the same account locally since we have yet to submit the transaction. Build() will increment the account sequence locally but we can manually decrement or set the sequence value to override after each build()
– Momentus Mitch
Aug 20 at 16:40












What you do is what Paul and I have been saying all along..
– Johan Stén
Aug 21 at 4:43





What you do is what Paul and I have been saying all along..
– Johan Stén
Aug 21 at 4:43


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstellar.stackexchange.com%2fquestions%2f1482%2fhow-to-let-users-decide-between-transactions%23new-answer', 'question_page');

);

Post as a guest
































































Comments

Post a Comment

Popular posts from this blog

What does second last employer means? [closed]

Image
Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
Read more

List of Gilmore Girls characters

Image
The season three cast—(Back row): Lane, Michel, Paris, Emily, Richard, Sookie, Miss Patty, Kirk; Front row: Jess, Luke, Lorelai, Rory, Dean This is a list of characters for the comedy-drama television series Gilmore Girls . Contents 1 Main characters 1.1 Lorelai Gilmore 1.2 Rory Gilmore 1.3 Sookie St. James 1.4 Lane Kim 1.5 Michel Gerard 1.6 Luke Danes 1.7 Emily Gilmore 1.8 Richard Gilmore 1.9 Paris Geller 1.10 Dean Forester 1.11 Jess Mariano 1.12 Kirk Gleason 1.13 Jason Stiles 1.14 Logan Huntzberger 2 Major recurring characters 2.1 Christopher Hayden 2.2 Jackson Belleville 2.3 Mrs. Kim 2.4 Tristin DuGray 2.5 Max Medina 2.6 Taylor Doose 2.7 Dave Rygalski 2.8 Marty 3 Recurring characters 3.1 Stars Hollow 3.2 Chilton 3.3 Yale 3.4 Other 4 Notable guest stars 5 Unseen characters 6 Notes 7 References Main characters Actor Character Appearances Season 1 Season 2 Season 3 Season 4 Season 5 Season 6 Season 7 A Year in the Life Lauren Graham Lorelai Gilmore...
Read more

Confectionery

Image
Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of ...
Read more