|
JeanLuc
For 0.8.0 could you possibly do something about the use of the *current directory*, for the old NRS client it seemed fine to base the database location (among other things) on the user's current directory. For a cross platform desktop application that leads to all kinds of troubles.
Since we are using the same vm instance for both the client and NXT we have to instruct users how to open the client. They must navigate to such and such folder before they double click the launcher.
All this would be solved if you'd use some form of externally settable property for things such as database location.
Thanks for posting the 0.8.0 api! It's been of help already.
|
|
|
|
@CFB and others, would it be good if assets listed on exchange were somehow grouped? To bring order to the chaos. Some generic groups such as "currency", "ipo", etc..
Will this help if u have 1000 assets in a group? At first ,i thinked asset should has many feathers: like type,brand but now, assets in nxt have simple contents may be better, nxt asset in layer 1 because like type,brand,group of asset ,client (layer 2)can sort or group them. There is no need for this. Assets, Transactions, Accounts all have global unique identifiers clients can store anything they want with that as long as they store it themselves. It would be bad to put this in the protocol. |
|
|
|
|
Could someone please tell me what is the valid (possible) range of NXT account numbers? It seems you can make transactions to account number 1 for instance but what is the chance of someone actually selecting a private key that translates to an account number of 1, or is this not possible at all?
Thank you.
|
|
|
|
We included the ability to start and stop Jetty since we like the user to be able to delete the blockchain and start-fresh from a command in the UI
Re-init after shutdown will be tricky to support for me, because in many places I have init-once only singletons or static blocks, but for this use case I can probably provide a Nxt.fullReset() method that just deletes the genesis block from the database (and if I can trust the database triggers, this should wipe the rest of it too). What can you say about the status of the database, will it remain H2 and will this remain an internal implementation or do you see developers accessing or updating data in the database them selves?
I am not changing anything about the database. Some people have asked me about using mixed-mode for it, where a tcp server is started automatically and external processes can connect to it. I don't want to enable this by default for security and performance reasons, but I will make the database jdbc url a parameter in the nxt.properties so that client developers can do such tricks in their customized distributions. It is not possible to restrict db access to read-only for such an external process, so if you abuse that and write to the db expect things to break. Also, regarding custom colored coins. Will you be doing some more standardization in that area? Will there be more work towards an API to work with *custom* attachments? Not that it's strictly needed just wondering if you had ideas in that area.
Haven't thought about this at all yet. But yes, I realize that transaction attachment types don't need to be all hardcoded, one day you can have custom attachment types that just need to conform to some API, and not even need to be supported by all clients. Thanks and that all sounds perfect. Will Nxt.fullReset() be in 0.8.0? |
|
|
|
My current setup is that i use embedded jetty and feed the Nxt servlet on startup to jetty.
What's the setup you use for jetty? Will i still need to embed my own or will 0.8.0 take care of that?
You shouldn't need to deal with jetty directly. You call Nxt.init() which will trigger all initializations, and will start the jetty servlets it needs (if nxt.shareMyAddress=false, it will not start the PeerServlet, if nxt.enableUIServer=false it will not start the UserServlet for the NRS UI), and is safe to call multiple times. Then, there will be Nxt.getBlockchain(), Nxt.getBlockchainProcessor() and Nxt.getTransactionProcessor() to get hold of the corresponding singletons. The init adds a shutdownHook to handle stopping the threads and closing the database at the jvm shutdown, I assume you never need to shutdown it explicitly once started until the application exit. That's a lot of changes I am going through, so 0.8.0e should come out some time next week, and I will have to keep it compatible with 0.7.6 peers until client packagers and developers transition to 0.8.0. We included the ability to start and stop Jetty since we like the user to be able to delete the blockchain and start-fresh from a command in the UI we also used a shutdown hook but then to gracefully take down jetty so Nxt had time to shut down and write everything from memory. As i understand it you now have all cleanup code in a shutdown listener of your own, thats nice. I believe so to that there is no use for a shutdown/startup sequence in a single jvm session, just restart jvm and your done. What can you say about the status of the database, will it remain H2 and will this remain an internal implementation or do you see developers accessing or updating data in the database them selves? Also, regarding custom colored coins. Will you be doing some more standardization in that area? Will there be more work towards an API to work with *custom* attachments? Not that it's strictly needed just wondering if you had ideas in that area. |
|
|
|
|
JeanLuc
You said you now use embedded jetty. My current setup is that i use embedded jetty and feed the Nxt servlet on startup to jetty.
What's the setup you use for jetty? Will i still need to embed my own or will 0.8.0 take care of that?
|
|
|
|
Will the interfaces for the major components (Account, Transaction, Peer etc..) stay roughly the same?
Also the listener interfaces, will they remain?
Some of them. There are two big changes. First, Nxt is no longer a servlet and does not need to follow the servlet init/destroy lifecycle anymore. It is initialized reading its properties from nxt.properties instead of web.xml. If needed, it will start a PeerServlet that accepts peer-to-peer requests, an APIServlet that serves http/json API requests, and a UserServlet that supports the current NRS javascript client. You can disable all of those in the properties file, so if you are only using the Java API, and don't have a public IP on which to accept incoming peer requests, you will not be running any servlets at all. Second, I am making Block, Transaction, and Blockchain, interfaces. The current Blockchain class is a bunch of static methods, I am splitting those into BlockchainProcessor, TransactionProcessor, and Blockchain/BlockchainImpl classes. All those will be singletons instead of collections of static methods, which I believe is more flexible in the long term. Peer has also been split into Peer (an interface), PeerImpl (package-local implementation), and Peers (static methods that handle the whole set of peers). Account, Asset, Order, Alias, etc, will not change for now. In the future I will have to move them to the database, so I don't want to waste time refactoring them now only to change them again later. I will try to keep the Listener interfaces, and see how I can use them to accommodate your request for monitoring the initialization steps too. Sounds cool! When do you expect to release 0.8.0? Also the setup where you split out the actual peer handling and the pure blockchain interface is perfect, it would allow for even better tools to analyze the blockchain. |
|
|
|
Ideally there would be a listener you could register or some sort of progress monitor. In eclipse you have the IProgressMonitor interface, such an interface would be perfect, i included a simplified example.
public interface IProgressMonitor {
public void beginTask(String name, int totalWork);
public void done();
public void worked(int work);
}
The monitor would be provided by the user and is passed to the various startup methods. When reading the blockchain (for instance) you would call monitor.beginTask("Read blockchain", totalNumberOfBlocks) and then on each (or each 5th, 10th etc.) block read you call monitor.worked(numberOfBlocksRead). At the end you would call monitor.done().[/i]
A listener for log messages would be very nice to. I now remove the nxt.util.Logger class and replace with my own in order to display messages in the dialog that displays startup progress. Not a clean solution at all.
I will keep that in mind. I am making a lot of changes in 0.8.0. Will think about how to do it when I get to it. Will the interfaces for the major components (Account, Transaction, Peer etc..) stay roughly the same? Also the listener interfaces, will they remain? |
|
|
|
|
JeanLuc:
I posted this a couple of days ago. I still look forward to your reply.
Currently there is no way for java clients to get notified of progress during startup (nxt.Nxt.init())
Ideally there would be a listener you could register or some sort of progress monitor. In eclipse you have the IProgressMonitor interface, such an interface would be perfect, i included a simplified example.
public interface IProgressMonitor {
public void beginTask(String name, int totalWork);
public void done();
public void worked(int work);
}
The monitor would be provided by the user and is passed to the various startup methods. When reading the blockchain (for instance) you would call monitor.beginTask("Read blockchain", totalNumberOfBlocks) and then on each (or each 5th, 10th etc.) block read you call monitor.worked(numberOfBlocksRead). At the end you would call monitor.done().
A listener for log messages would be very nice to. I now remove the nxt.util.Logger class and replace with my own in order to display messages in the dialog that displays startup progress. Not a clean solution at all.
Thanks!
|
|
|
|
Question about the java API.
Are there any plans to extract the functionality of the handlers in in nxt.http into java interfaces.
My use case is to create a payment transaction but i dont want to go through the HTTP layer. Currently to send money from the java api you would have to duplicate all the steps taken in for instance nxt.http.SendMoney.
The Java API is still a work in progress, in fact I am just in the middle of another refactoring for 0.8.0. I am switching to embedded jetty, so Nxt will no longer be a servlet. I will also improve the API while at it. For the SendMoney example, what kind of an API would you find useful? Right now the steps you would need to duplicate are not that many, basically you need to do: Transaction transaction = Transaction.newTransaction(Convert.getEpochTime(), deadline, publicKey,
recipient, amount, fee, referencedTransaction);
transaction.sign(secretPhrase);
Blockchain.broadcast(transaction);
The rest is validating the user input and returning error messages, which is application specific. If you submit an invalid transaction, it will not be accepted, and a lot of validation is done immediately when the Transaction object is constructed (such as for non-negative amount and fee, deadline, timestamp). Other validations, such as the account having enough funds are only done when the Transaction is about to be included in a block (because the account balance may have changed in the meantime). Hi! You are right the steps to send money are very limited indeed, i already went ahead and did things that way. Looking at it now i no longer think there should be a higher level api apart from what is provided. While i have your attention might i point you to the following.. Currently there is no way for java clients to get notified of progress during startup (nxt.Nxt.init()) Ideally there would be a listener you could register or some sort of progress monitor. In eclipse you have the IProgressMonitor interface, such an interface would be perfect, i included a simplified example. public interface IProgressMonitor { public void beginTask(String name, int totalWork); public void done(); public void worked(int work); } The monitor would be provided by the user and is passed to the various startup methods. When reading the blockchain (for instance) you would call monitor.beginTask("Read blockchain", totalNumberOfBlocks) and then on each (or each 5th, 10th etc.) block read you call monitor.worked(numberOfBlocksRead). At the end you would call monitor.done(). > I am switching to embedded jetty That's how we have done it from the start. But what is wrong with the servlet, should you not stay far from jetty and focus solely on nxt core? Nice to meet you btw.. You did a nice job on the refactorings. |
|
|
|
|
Question about the java API.
Are there any plans to extract the functionality of the handlers in in nxt.http into java interfaces.
My use case is to create a payment transaction but i dont want to go through the HTTP layer. Currently to send money from the java api you would have to duplicate all the steps taken in for instance nxt.http.SendMoney.
|
|
|
|
Hi,
I'm developing AE UI but against the java api, not the json api. How would i go about that? Can i get a copy of the test nxt blockchain (if there is any) or the class files used on holms.cloudapp.net:6874?
Thanks!
http://holms.cloudapp.net:6874/testnxt.zipThanks! |
|
|
|
|
Hi,
I'm developing AE UI but against the java api, not the json api. How would i go about that? Can i get a copy of the test nxt blockchain (if there is any) or the class files used on holms.cloudapp.net:6874?
Thanks!
|
|
|
|
Hi, I cant seem to find any information on the http://wiki.nxtcrypto.org/wiki/Nxt_API about the getNewData request. Also looking in the source for 0.7.4 it seems to be missing. Is that API removed? Thanks, It will be removed, do not use it. Thanks. And what about getInitialData? And where can i find more info on API plans/roadmap. Also will be removed, only info available is at thenxtwiki.org (programmers/api) Lol. all these wikis, thanks! |
|
|
|
Hi, I cant seem to find any information on the http://wiki.nxtcrypto.org/wiki/Nxt_API about the getNewData request. Also looking in the source for 0.7.4 it seems to be missing. Is that API removed? Thanks, It will be removed, do not use it. Thanks. And what about getInitialData? And where can i find more info on API plans/roadmap. |
|
|
|
Hi, I cant seem to find any information on the http://wiki.nxtcrypto.org/wiki/Nxt_API about the getNewData request. Also looking in the source for 0.7.4 it seems to be missing. Is that API removed? Thanks, |
|
|
|
|
The NXT servlet collected state information about each user that the user than later received when doing a getState request.
Is it correct that there is no such thing for the AE?
In other words is there a getState equivalent for AE?
|
|
|
|
I'm updating the testnet...
Is that why it's offline now? Could I also get some test nxt please 16372495462152719802 |
|
|
|
|
Show Posts
